fleet-dispatch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CALLE_API_KEY | No | CALL-E API key. Required unless dry run mode is enabled (FLEET_DISPATCH_DRY_RUN=1). Create at https://dashboard.heycall-e.com/account/api-keys | |
| FLEET_DISPATCH_PHONE | No | Your phone number in E.164 format. The only number this server will ever dial. | |
| FLEET_DISPATCH_LOCALE | No | Optional BCP 47 locale hint, e.g. en-IN. | |
| FLEET_DISPATCH_REGION | No | Optional country code hint for routing, e.g. IN. | |
| FLEET_DISPATCH_DRY_RUN | No | Set to '1' to enable dry run mode, which answers with the first option without dialing. Use instead of CALLE_API_KEY. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| call_meA | Place a real phone call to the engineer who owns this session and block until they answer. Use only when you are blocked on a decision that they must make: ambiguous spec, destructive or irreversible action, failing migration, spending money. Never for lint, style, or anything you can decide from the code. The call costs money and interrupts a person. Returns their spoken decision as JSON. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool available, there is no possibility of confusing it with another. The tool's purpose is clearly described and unique within the server.
The single tool name 'call_me' follows a verb_noun pattern, but with only one tool there is no established pattern to evaluate for consistency. It is internally consistent but offers limited evidence of a naming convention.
The server is named 'fleet-dispatch', implying a broad dispatch domain, yet it exposes only a single tool for calling an engineer. This is far too few tools for the apparent scope and leaves the core functionality unaddressed.
The tool surface is severely incomplete for a fleet dispatch server—there are no tools for managing fleets, routes, vehicles, or dispatches. The single call tool is an outlier that does not cover the domain implied by the server name.