Flitware

Get one document metadata record (never file bytes or URLs). Use when details of a known document id are needed. Example: {"id":"<document_id>"}.

document_get_metadata

List document metadata (never file bytes or URLs). Use when checking expirations or finding a document before requesting a download. Example: {"due_before":"2026-12-01","page":1,"perPage":20}.

document_list_metadata

Documents related to a vehicle and/or driver, with validity at a date. Use when checking expirations for a vehicle or driver before a readiness decision. Example: {"fleet_id":"<fleet_id>","as_of":"2026-10-29"}.

document_related_list

Closed domain values: statuses, types, priorities, currencies and per-operation values. Use when validating enum inputs before a filtered call; page/perPage slice single-catalog values (absent returns all). Example: {"catalog":"currencies"}.

domain_catalogs

Get one driver with assignment and masked contact. Use when reading assignment and status of a known driver. Example: {"id":"<driver_id>"}.

driver_get

List tenant drivers (operational fields, masked contact). Use when finding a driver before assigning or checking documents. Example: {"q":"gar","page":1,"perPage":20}.

driver_list

Find duplicate expense candidates (read-only). Searches EXPENSE items of one service by counterparty (fleet xor contact), total and date window; page/perPage are optional (absent returns all). Example: {"service_id":"<id>","fleet_id":"<id>","occurred_at":"2026-10-28","total_cents":5000,"category":"fuel"}.

expense_duplicate_check

Register a fleet expense for a vehicle with duplicate check. Charges a service_item of type EXPENSE to an existing service (service_id required) linked to exactly one fleet (plate) or contact (third party). total_cents are minor units (150000 COP pesos = 15000000); currency must be ISO (COP, USD, EUR) and match the service currency (never converted); category one of fuel, tolls, parts, maintenance, other. Example: {"service_id":"<id>","fleet_id":"<id>","occurred_at":"2026-10-28","total_cents":5000,"currency":"COP","category":"fuel"}. Preview first; run expense_duplicate_check when unsure.

expense_register

Get one fleet vehicle by id (tenant-scoped, 404 when foreign). Use when details of a known vehicle id are needed. Example: {"id":"<fleet_id>"}.

fleet_get

List fleet vehicles of the caller's tenant. Use when the operator asks which vehicles exist or must pick one by plate or group. Example: {"plate":"TST","page":1,"perPage":20}.

fleet_list

Odometer/hourmeter history of one fleet vehicle. Use when mileage or hours over a period are needed (cost per km, meter gaps). Example: {"fleet_id":"<fleet_id>","meter_type":"ODOMETER","from":"2026-01-01","to":"2026-10-29"}.

fleet_meter_history

Per-vehicle operational summary: documents, meter age, checklists, work orders, assignments. Sections gated by caller scopes. Use when briefing one vehicle before dispatch or review. Example: {"fleet_id":"<fleet_id>"}.

fleet_operational_summary

Vehicle readiness for a date: documents, maintenance due, checklists, conflicts, driver. PASS/FAIL/UNKNOWN per check. Use when deciding if a vehicle may operate on a date. Example: {"fleet_id":"<fleet_id>","date":"2026-10-30"}.

fleet_readiness_check

Cancel a PENDING/RETRY own job. Use when the operator no longer needs a queued job to run. Example: {"job_id":"<id>"}. Preview first, then execute; only PENDING or RETRY jobs can be cancelled.

job_cancel

Get one own job (tenant-scoped). Use when the operator checks the status, attempts, or result of a background job it owns. Example: {"job_id":"<id>"}. Only the creator or ROOT may read it; anything else answers 404.

job_get

Retry a FAILED own job after reconcile. Use when the operator requeues a failed job once the cause is understood. Example: {"job_id":"<id>"}. Preview first; ambiguous outcomes park for the operator instead of auto-retrying.

job_retry

Explained maintenance analytics: cost per km/hour, recurrent failures, vehicle comparison, MTTR by vendor, document risk, PM compliance detail. Use when explaining spend, failures or compliance with formulas and coverage; page/perPage are optional over rows (absent returns all); envelope "v2" wraps the payload with status, coverage and renewal guidance for document_risk. Example: {"analysis":"cost_per_km","from":"2026-07-01","to":"2026-10-29"}. Cost figures are null with cost_calculable false when no closed orders back them; a 0 arrives only with real evidence.

maintenance_analysis

Six-month maintenance dashboard aggregates (status/type/priority, created/closed, cost). Use when summarizing workload and spend trends. Example: {}.

maintenance_metrics

Operational maintenance counts (open orders, critical issues, out of service, overdue/due soon). Use when answering what needs attention today. Example: {}.

maintenance_overview

Policy-backed reliability metrics (MTTR/MTBF/availability/PM compliance). Use when availability or repair performance is questioned; needs a published KPI policy. Example: {"from":"2026-01-01","to":"2026-10-29"}.

maintenance_reliability

Preventive schedule states per vehicle (OVERDUE/DUE_SOON/SCHEDULED/...). Use when planning upcoming maintenance; page/perPage are optional (absent returns all). Example: {"page":1,"perPage":20}.

maintenance_schedule

Assign a resource to a work order (PLANNED, anti-overlap). Use when the planner books a bay, lift, or technician for a work order window. Example: {"resource":"<id>","work_order":"<id>","starts_at":"2026-11-03T08:00:00-05:00","ends_at":"2026-11-03T12:00:00-05:00","planned_hours":4}. Preview first; overlapping PLANNED windows are rejected.

maintenance_schedule_create

Daily operations review: blocks, warnings and info gaps with evidence and actions. Deterministic versioned rules. Use when opening the day or triaging what needs attention; page/perPage are optional (absent returns all findings, counts stay global). Example: {"horizon_days":7}.

operations_review

Triage daily operations findings into executable, pending approval, manual or blocked with evidence, deduped open work orders and next steps. Use when the operator asks what needs attention today or what to do about a finding. Example: {"horizon_days":7}.

operations_triage

Tenant subscription access mode (works in any mode). Use when gating features or explaining blocked access. Example: {}.

plan_status

Tenant plan usage vs limits (ROOT only, full or recoverable). Use when checking quota consumption. Example: {}.

plan_usage

Read the portal contact's own profile and services. Use when the authenticated contact asks for their profile or services. Example: {"page":1,"perPage":20}. Requires a bound portal contact JWT; page/perPage are optional (absent returns all services).

portal_contact_read

Read the portal driver's own profile, services and vehicle. Use when the authenticated driver asks for their assignments or vehicle. Example: {"page":1,"perPage":20}. Requires a bound portal driver JWT; page/perPage are optional (absent returns all services).

portal_driver_read

Monthly cost report for one vehicle with chart hint, CSV and markdown fallback. Use when explaining one vehicle's maintenance spend over a date range. Example: {"fleet_id":"<fleet_id>","from":"2026-08-01","to":"2026-10-29"}. page/perPage are optional (absent returns all months). Months without closed orders report cost_minor null with cost_calculable false; a 0 arrives only with backing orders.

report_vehicle_costs

Get one scheduled execution with its delivery summary. Use when inspecting a single delivery, delta or error. Example: {"id":"<run_id>"}.

scheduled_run_get

List execution history of a scheduled task (deliveries: summary + evidence + errors). Use when auditing what an automation delivered; limit caps the window (default 20, max 50) and page is optional (absent is the first window). Example: {"task_id":"<task_id>","limit":20}.

scheduled_run_list

Create a persistent scheduled task (v1: read-only maintenance analyses). Use when automating a daily review, readiness check or analysis. Example: {"name":"rev-diaria","task":"operations_review","params":{"horizon_days":7},"schedule":{"kind":"DAILY","time":"08:00"},"preview":true}.

scheduled_task_create

Delete a scheduled task and its execution history (owner or ROOT). Use when retiring an automation that is no longer needed. Example: {"id":"<task_id>","preview":true}.

scheduled_task_delete

Get one scheduled task with its schedule, params and fire state. Use when reading thresholds and next fire of a known task. Example: {"id":"<task_id>"}.

scheduled_task_get

List the tenant's scheduled MCP tasks (persistent automations, v1: read-only analyses). Use when reviewing automations before pause, resume or delete; page/perPage are optional (absent returns all, total stays global). Example: {}.

scheduled_task_list

Update a scheduled task (owner or ROOT): name, status (pause/resume), schedule or params. Use when pausing, resuming or retuning an automation. Example: {"id":"<task_id>","status":"PAUSED","preview":true}.

scheduled_task_update

Cross-domain search with per-domain scope gate (zero hits and zero counts without scope). domains uses singular names (fleet, service, maintenance, document, checklist, support) and requires at least one. Use when one query must span fleets, services, maintenance, documents, checklists or support tickets. Example: {"q":"frenos","domains":["maintenance","service"]}. Domains without scope return zero hits and zero counts.

search_global

Evaluate vehicle candidates for a service date: documents, maintenance, checklists, schedule clashes, driver and service fit, with 1-3 explained alternatives. Use when the operator must pick a vehicle for a service or a re-assignment. Example: {"date":"2026-10-30","fleet_ids":["<fleet_id>"]}.

service_candidate_evaluate

Create a PENDING service for a tenant contact. Use when the operator books a new trip or job for a customer. Example: {"contact_id":"<id>","scheduled_at":"2026-11-01T08:00:00-05:00","origin_address":"Calle 1","destination_address":"Calle 2","currency":"COP"}. Preview first, then execute; duplicates need human approval, never auto-reject.

service_create

Get one service by id with PII-masked notes, vehicle/driver refs and items. Use when drilling into a service picked from a list. Example: {"id":"<service_id>"}.

service_get