DroneBundle

Get the full details of one invoice (financial).

get_invoice

Get the full details of one job, including assigned pilots.

get_job

Get one maintenance record in full, including its status history. It references equipment_id and schedule_id as ids: use get_equipment or get_maintenance_schedule to resolve their names.

get_maintenance_record

Get one maintenance schedule in full by its id, including its current progress and due status.

get_maintenance_schedule

Get one drone map, including processing progress, skipped photos, reconstruction statistics, and available deliverables. Requires the project, job, and scan ids.

get_scan

Get one pilot's full dossier by id: profile, assigned equipment, assigned jobs and their projects, flights flown with total flight time and distance, and related documents.

get_pilot

List a pilot's scheduled job occurrences (their upcoming and past assignments), grouped by project. Use the tab to choose today, upcoming, or all. Pages with has_more / cursor.

get_pilot_assignments

Check who is free using saved working hours, date exceptions and flight bookings. Omit pilot_ids to check the active pilot roster automatically, including managers who also fly. Use pilot_query to find a name or email directly, without searching other tools. Returns named results with confirmed_free_periods and totals; never call not_confirmed_periods available. For this week use period this_week, for next week use next_week: the server resolves Monday through Sunday. Returns up to 10 pilots per page; follow cursor with the same filters until has_more is false. Only admins and project managers. Snapshot of the active workspace, not external calendars or a reservation.

get_pilot_availability

Read planned shifts and hours, preferred shifts, declared availability and unbooked periods for pilots over up to 7 days. Use pilot_query for a name/email; ambiguous names require clarification. Omit pilot filters for all active pilots, including managers who fly. Returns 10 per page: follow every cursor before comparing hours across the roster. Working hours, preferred shifts, planned shifts and existing bookings are separate. Several dock assignments can overlap; do not invent a pilot capacity limit. Read get_shift_coverage for the actual jobs and flights.

get_pilot_shift_plan

Get the full details of one project, including its jobs and counts. flights_flown_count counts flown flights with no manager sign-off outstanding. project_area holds the site size in square meters and its perimeter in meters when an area is drawn.

get_project

Who can see a project besides the internal team: the client companies given access, with their access level, and the ops leads assigned to it. ops_leads is null when the user is not allowed to see ops leads.

get_project_access

Read a project's discussion thread (the Discussion tab on the project page). Returns messages oldest-first with sender names. Messages flagged expired or protected have hidden content: report them as hidden, never guess what they said. Pages with has_more / cursor.

get_project_discussion

Get one safety audit in full by its id, including its checklist, findings, and corrective actions.

get_audit

Get the full details of one safety incident.

get_incident

Get the full details of one safety risk.

get_risk

Read actual jobs and individual flights within workspace shifts, their assigned pilot ids, and flights still needing pilots. Includes the next morning for overnight shifts. Each job uses its own timezone. Optional name filters match all jobs/shifts containing the text; do not silently select one ambiguous job. Only flights with scheduled status and no pilots count as gaps. staffing_gaps separates timed, untimed and combined flight counts; a scheduled status does not imply a time is set. Summary totals are complete; follow next_offset only for individual flight details. Does not assign anything or establish how many simultaneous docks a pilot can operate.

get_shift_coverage

Read the workspace shift names and start/end times. Overnight shifts belong to the day they start. Read this before interpreting names such as Morning or Night.

get_shift_presets

Get weather for an authorized DroneBundle job or project site. First call list_job_weather_locations and pass its location_id. Keep hours and days small (for example 12 hours or 3 days) so the answer stays readable.

get_weather

Get the details of one team member.

get_team_member

List the equipment assigned to one job, one project, or one pilot, with equipment and pilot names included. Provide exactly one of job_id, project_id, or pilot_id. Category, status, and paging apply to the pilot scope only.

list_assigned_equipment

List CRM deals (sales pipeline). Optionally filter by stage, assigned user, client company, or label (only one filter applies per call). Pages with has_more / cursor.

list_deals

List client companies in the workspace. Pages with has_more / cursor.

list_client_companies

List the client contacts belonging to one client company. Requires client_company_id. Pages with has_more / cursor.

list_clients

List documents from the workspace-level Documents section only. Files uploaded to a project or job are separate: use list_project_files or list_job_files for those. Each document carries expiry: what was read from the file for expiry tracking (insurance, registrations, pilot certificates, training, permits), with a status, the next expiry date, days_until_expiry counted from today (zero or negative means expired) and one entry per certificate or policy found, giving holder, issuer, number, aircraft serial, course, issue date, valid-from date, expiry date, validity terms and restrictions. expiry_summary counts the documents on the page by status. Use this for any question about expired, expiring or valid documents; never judge expiry from a file name. Optionally filter by category. Pages with has_more / cursor: read every page before saying what has or has not expired.

list_documents

List equipment (drones, controllers, batteries, and other gear). Optionally filter by category. Pages with has_more / cursor.

list_equipment

List scheduled flights by stored status, newest first, with job name and priority attached. Status values: scheduled (no outcome yet), completed (flown: the pilot submitted the report or a flight log recorded it automatically), approved (flown and signed off by a manager), rejected (returned to the pilot for changes), not_flown. Manual approval is optional and off by default; manual_approval says whether it is on. A completed flight waits for a manager only when its pending_approval is true, so for "what needs approval" filter by status completed and keep only pending_approval true. For flight reports, outcomes, report answers and totals over a date range, prefer list_flight_reports. Flown flights carry the pilot's note as completion_notes and the report answers as flight_details (label/value pairs). Pages with has_more / cursor.

list_flight_approvals

List drone flight logs for the workspace, newest first. Optionally narrow to a single project, job, pilot, or drone (only the most specific filter applies). Pages with has_more / cursor.

list_flights

The Flight Reports page: every scheduled flight in a date range (at most 92 days) with its outcome and report. Use it for what was flown or not flown, why, flight report answers and their totals (for example birds counted), what needs review, verification by flight logs, billing counts and per-job breakdowns. Flights are recorded two ways: the pilot submits a report, or a flight log from a dock, the controller app or an upload matches the scheduled flight and records it automatically (recorded_automatically). flight_log says whether a log verified the flight. report_status is one of Upcoming, Missing outcome (overdue with no result), Returned, Log says flown (marked not flown but a log matched), Missing answers (required questions unanswered), Pending approval, Approved or Complete; needs_review marks the first five kinds. Manual approval is optional and off by default (manual_approval says which): while off, a submitted report is complete and never waits for sign-off. billing applies the workspace billing rules (billing_rules): Included, Excluded by billing rules, Held until approved, Not yet due or Not counted. report_questions lists the workspace's report questions (id, type, choices, required, and the jobs they apply to). summary and by_job cover every flight matching the filters, independent of paging; summary.report_answers totals the report answers on flown flights. Pages with has_more / cursor.

list_flight_reports

List invoices in the workspace (financial). Pages with has_more / cursor.

list_invoices

List the files uploaded to one job. Needs the job id and the job's project id (from get_job, list_jobs, or the page context). Optionally filter by category or search by file name. Newest first. Pages with has_more / cursor.

list_job_files

List jobs across the whole workspace, or a single project, with real filters applied in the query (not per page). Combine any of: status, job type, priority, assigned pilot, unassigned, overdue, and a start-date range. Jobs moved to follow ups (parked) are left out by default, along with every job in a parked project: pass parked true to list exactly those instead (a search query matches parked jobs too). This returns at most one page — up to 200 jobs, 50 by default — never the whole workspace at once. Use total (the full count of matches) to tell the user how many there are; when total is large, narrow it down with filters rather than paging through everything. Only raise offset to fetch another page when the user genuinely needs more. To filter by a person, first get their id from list_team and pass it as pilot_id.

list_jobs

List maintenance records (completed and pending service log entries) for the workspace. Optionally filter by status or equipment. Pages with has_more / cursor.

list_maintenance_records

List equipment maintenance schedules, each with its computed progress and whether it is ok, due soon, or overdue. Optionally filter by status or equipment. Pages with has_more / cursor.

list_maintenance_schedules

List flights a manager explicitly approved through manual approval. Manual approval is optional and off by default, so most flown flights never appear here: use list_flight_reports for flights flown, report answers and counts. Use this only for questions about manager sign-off. Optionally filter by project, job, pilot, or a date range. Each flight carries the pilot's note as completion_notes and the report answers as flight_details (label/value pairs). Pages with has_more / cursor.

list_approved_flights

List drone maps (also called scans) across the workspace and their processing status. Filter by all, active, ready, or failed. Results include the related project and job plus a cursor when more maps are available.

list_scans

List the workspace pilots with each one's stats: jobs assigned / in progress / completed, active projects, and assigned drones. For flights a pilot flew, use get_pilot or list_flight_reports with pilot_id. Pages with has_more / cursor.

list_pilots

List the files uploaded to one project's Files tab (project-level files, not workspace documents and not job files). Newest first. Pages with has_more / cursor.

list_project_files

List the projects in the workspace. Archived projects and projects moved to follow ups (parked) are left out by default: pass archived true or parked true to list exactly those instead. Pass pinned true to list the projects the current user has starred. Pass status to filter by status. Pass a cursor to get the next page.

list_projects

List safety/compliance audits for the workspace (title, type, status, due date, lead auditor, findings count). Optionally filter by status or audit type. Pages with has_more / cursor.

list_audits

List safety incidents. Optionally filter by status, category, or severity. Pages with has_more / cursor.

list_incidents