LogiSwarm AI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_MODEL | No | Google Gemini model name to use for multimodal vision and conversational responses. | gemini-2.5-flash |
| GEMINI_API_KEY | No | Google Gemini API key. Optional; when not configured, offline fallback behavior is used for multimodal vision and conversational responses. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_fleet_statusB | Returns telematics, current locations, payloads, and status of all fleet vehicles. |
| optimize_cvrp_routesB | Executes multi-agent Capacitated Vehicle Routing optimization taking into account weight, volume, deadlines, and EV prioritization. |
| inject_disruptionB | Simulates a supply chain crisis (breakdown, severe_weather, road_closure, urgent_surge) and triggers self-healing rerouting. |
| inspect_cargo_multimodalB | Performs Google Gemini multimodal vision inspection on cargo damage or shipping labels. |
| evaluate_feedback_loopA | Audits current logistics plan and returns SLA, green carbon, and load balance critique scores. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| dispatcher_briefing | Generates a tactical morning briefing for dispatchers with fleet availability and pending order volume. |
| disruption_postmortem | Analyzes root causes and recovery actions following a simulated supply chain crisis. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Fleet Telematics & Status | Real-time positions, telemetry, battery, and capacity of all active fleet vehicles |
| Logistics Hubs & Depots | Central warehouse and regional distribution hubs with geographic coordinates and capacities |
| Open Priority Consignments | Active orders, delivery coordinates, deadlines, and SLA penalty weightings |
TDQS
Scored across 5 tools
Each tool targets a clearly distinct function: fleet status retrieval, route optimization, disruption simulation, visual cargo inspection, and plan auditing. There is no overlap or ambiguity between them.
All names use a consistent verb_noun snake_case pattern (get_fleet_status, optimize_cvrp_routes, inject_disruption, inspect_cargo_multimodal, evaluate_feedback_loop). Minor irregularity: the verb 'optimize' and acronym 'cvrp' differ slightly in style but remain readable and predictable.
Five tools is well-scoped for a focused logistics optimization server. Each tool earns its place by covering a distinct stage of the fleet management and disruption-handling workflow.
The surface covers fleet status, optimization, disruption handling, inspection, and evaluation, forming a coherent lifecycle for logistics operations. Minor gap: no explicit tool for committing or exporting the final optimized routes/plan, though evaluation may implicitly cover this.