last-mile-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_customerB | Find customers by name or id. Returns id, name, sector, sites, contract. |
| customer_ticketsB | Service tickets for a customer, newest first. |
| customer_invoicesC | Invoices for a customer with their payment state, newest first. |
| account_healthA | One joined view of a customer: contract, open tickets, overdue balance. Needs both read grants. A caller holding only one gets a refusal rather than a half-answer, because a health summary missing its billing half reads as good news. |
| open_ticketB | Open a service ticket. Internal and reversible, so it executes directly. |
| prepare_invoiceA | Prepare an invoice. It is held as a draft and is NEVER issued by this server. An issued invoice reaches the customer and cannot be recalled, so it is the canonical irreversible action: the tool prepares, a human issues. |
| my_draftsC | Everything this caller has prepared and not yet confirmed. |
| whoamiA | The identity and grants this call runs as. Present in every deployment. When someone reports that a tool "does not work", the first question is which token they are on, and the answer should not require reading a database. |
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 8 tools
Each tool serves a distinct purpose: customer lookup, ticket listing, invoice listing, combined health view, ticket creation, invoice draft creation, draft listing, and identity/grants. No two tools overlap in intent, and the descriptions clarify any potential ambiguity (e.g., account_health explicitly combines data from other tools).
Naming mixes verb-first (find_customer, open_ticket, prepare_invoice) with noun-first (customer_tickets, customer_invoices, account_health) and possessive (my_drafts, whoami). The pattern is readable but not consistent, lacking a uniform verb_noun or resource_noun structure.
8 tools is well-scoped for a customer service and billing domain. Each tool covers a core operation without unnecessary bloat, and the count feels neither thin nor overwhelming.
The surface covers customer lookup, ticket listing/creation, invoice listing/drafting, health summaries, and identity. Missing update/close actions for tickets or invoices, but these are intentionally excluded (e.g., invoice issuance is human-only), so the gaps are not fatal and agents can work within the design.