FastMCP server for a decentralized drone swarm search-and-rescue simulation in post-disaster Indonesia. Provides tools for fleet management, navigation, thermal sensing, swarm communications, and mission state tracking.
Strong tool naming (verb-first, clear intent) and comprehensive descriptions (avg 180 chars, well above 10-char minimum). All 20 tools have explicit schemas with typed parameters. However, several parameters lack descriptions (e.g., move_to's x/y lack range constraints in descriptions), and output schemas are not formally documented in the code. Error handling is present but inconsistent, some tools return structured errors, others omit recovery guidance. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications. Composition is excellent: tools chain well (discover_fleet → get_drone_status → move_to), and the interface matches agent intent (natural grid coords, drone IDs from discovery). Missing: formal output schema documentation, parameter constraint descriptions (ranges, enums), and error recovery hints.
Assign a mission role to a drone. Only the agent or the current leader should call this. Valid roles are: 'scout' (explore and scan), 'rescue' (deliver supplies to survivors), 'relay' (extend comm range), 'idle' (standby).
Broadcast a message from the leader to all drones in the swarm. Messages are delivered to all drones within COMM_RANGE. Use this to alert the fleet to survivor locations, supply drops, and mission status updates.
Classify a heat signature at a specific location. Returns the type (ambient, possible_human, human, fire), confidence score, and estimated survivor count. Use this to evaluate ambiguous thermal hits before committing to a rescue mission.
Confirm that a heat signature is a real survivor. Must be called BEFORE deploying rescue supplies. Returns confirmation status, survivor urgency level, and group size estimate. Confirmation requires the drone to be within CONFIRM_RADIUS cells of the target.
Discover all active drones on the network. Returns a list of drone IDs, current positions, battery levels, roles, and statuses. The agent MUST call this first — drone IDs are dynamically assigned and must not be hard-coded. Use the returned IDs for all subsequent tool calls.
Parameter descriptions lack constraint details. move_to's x/y parameters have no range (0 to GRID_WIDTH-1) in descriptions; assign_role's role param lacks enum constraint in description; thermal_scan lacks SCAN_RADIUS documentation. LLMs cannot read JSON Schema constraints, they rely on description text.
Output schemas not formally documented. Tools return dicts (e.g., discover_fleet returns {fleet, total_drones, active_drones, tick}) but no JSON Schema or field descriptions in docstrings. Agents cannot plan downstream calls without knowing response structure.
Error handling lacks recovery guidance. get_drone_status returns {error: 'Drone X not found'} but does not suggest calling discover_fleet(). assign_role returns invalid role error but omits valid role list in some paths. Errors should guide LLM to next action.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 68 | <=2025-11-25 | v2 |
Drop a supply package at a survivor's location. The drone must be adjacent (within 1 cell) to the survivor and must have loaded supplies via load_supplies() first. Returns confirmation of delivery and updates the survivor's status.
Trigger a leader election across the entire fleet. Each drone is scored on battery level (40%), active status (30%), sensor health (20%), and uptime (10%). The highest-scoring drone becomes the new leader. Call this at mission start and after any drone goes offline or its battery drops critically low.
Get detailed status of a single drone including position, battery, role, cargo, sensor health, uptime, and current move target.
Get the current fog-of-war state: which cells have been scanned and which remain hidden. Returns coverage percentage and a list of unrevealed sectors (5x5 blocks) with their coverage and centre coordinates. Use this to identify gaps in the swarm's coverage and redirect scouts.
Retrieve a cached heat map of the entire scanned area. Returns a 2D grid of temperature readings from all previous thermal_scan() calls. Useful for identifying patterns and planning the next sweep.
Retrieve all messages in a drone's inbox. Returns a list of messages received from other drones, including sender ID, timestamp, and message text. Use this to read field reports from scouts and status updates from other drones.
Get a complete snapshot of the world state: all drone positions, battery levels, roles, statuses, survivor locations, urgency levels, and rescue status. Use this for full-world awareness and mission planning.
Retrieve the mission log: a chronological record of all tool calls, drone movements, scans, confirmations, and supply drops. Useful for post-mission analysis and debugging.
Calculate the total battery cost and tick cost to move a drone from its current position to a target. Useful for planning long moves and checking if a drone has enough battery before committing to a move_to() call.
Query terrain properties at a specific grid cell or get the full terrain map. Returns terrain type, traversability, thermal properties, and movement cost.
Load rescue supplies onto a drone at the base station. The drone must be at (BASE_X, BASE_Y) and in ACTIVE or CHARGING status. Supplies are required before calling drop_supply(). Each drone can carry one supply package.
Command a drone to move to grid coordinates (x, y). Movement is NOT instant — the drone spends move_cost ticks crossing each cell, and battery drains by BATTERY_DRAIN_PER_MOVE per cell. The simulation is ticked for every step so survivors' urgency escalates in real time. Returns the final position, remaining battery, and total ticks consumed.
Immediately recall a drone to base for charging. The drone will autonomously navigate back to (BASE_X, BASE_Y) and enter CHARGING status. Use this when battery is critically low or the drone is stranded.
Send a direct message from one drone to another. The message is only delivered if the target drone is within COMM_RANGE of the sender. Use this for leader-to-drone task assignments and peer-to-peer coordination.
Execute a thermal scan centred on a drone's current position. Scans all cells within SCAN_RADIUS (circular). Returns a list of heat signatures with confidence scores and position estimates. Hits with confidence >= 0.7 are likely survivors; lower confidence readings are possible false positives.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Tools are marked READ_ONLY or WRITE in metadata but not in MCP tool definitions. Agents cannot infer safety/idempotency from tool schema alone.
Confirmation pattern missing for destructive operations. drop_supply and recall_drone modify state but lack dry-run or confirmation step. Agents can accidentally drop supplies or recall wrong drones without a safety gate.