resolve.mcp_server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RESOLVE_DB_PATH | No | SQLite database file (seeded on first start) | ./data/resolve.db |
| RESOLVE_MCP_CUSTOMER_ID | No | Customer the MCP server acts for | C-1001 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_customerA | Get the signed-in customer's profile and a list of their orders. Call this first when the customer refers to an order without giving its number, or asks about their account. |
| get_orderA | Get one order's status, items, totals, refund eligibility and shipping address. Call this before answering any question about a specific order, and before issuing a refund. |
| track_shipmentA | Get carrier, tracking number, delivery status, ETA and scan history for an order. Call this when the customer asks where a parcel is or when it will arrive. |
| search_help_centerA | Full-text search of the Northwind Gear help center (policies, shipping, warranty, sizing). Call this for any policy or how-to question before answering from memory. |
| update_shipping_addressA | Change the shipping address of an order that has not shipped yet. Only call this after the customer has given the complete new address; never guess missing parts. |
| issue_refundA | Refund part or all of an order to the original payment method. Policy (enforced by the tool): within 30 days of the order, never more than what is left to refund, and refunds over $100 are held for a human specialist's approval. Call get_order first to check amounts. |
| escalate_to_humanA | Open a ticket for the human support team. Call this when the customer asks for a person, for warranty claims, cancellations, or anything the other tools and policies cannot solve. |
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 7 tools
Each tool has a clearly distinct role: customer profile/order list lookup, single-order details, shipment tracking, policy search, address update, refund issuance, and human escalation. Overlap between lookup_customer and get_order is explicitly resolved by sequencing guidance, and track_shipment is clearly scoped to parcel status rather than general order details.
All tool names follow a consistent snake_case verb_noun pattern: lookup_customer, get_order, track_shipment, search_help_center, update_shipping_address, issue_refund, escalate_to_human. There are no mixed conventions or vague names.
Seven tools is well within the appropriate range for a focused customer-support order-resolution server. Each tool corresponds to a distinct support workflow need, and none appear redundant or filler.
The surface covers the full support lifecycle: identify customer/orders, inspect a specific order, track shipment, answer policy questions, update address pre-shipment, issue refunds with policy constraints, and escalate unsupported cases. Missing direct cancellation or warranty tools are intentionally handled through escalation, avoiding dead ends.