MCP Business Tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_SCOPES | No | Capability scopes for the server, e.g. "inventory:read,orders:prepare". The default capability is inventory read. | inventory:read |
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 |
|---|---|
| search_inventoryB | Search synthetic inventory. Does not mutate stock. |
| prepare_orderC | Prepare an expiring order proposal. Does not commit stock. |
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 2 tools
The two tools have clearly distinct purposes: one searches inventory and the other prepares an order proposal. There is no meaningful overlap or ambiguity in selecting between them.
Both names follow a consistent snake_case verb_noun pattern: search_inventory and prepare_order. The convention is predictable and easy to extend.
Two tools is quite thin for a server framed broadly as MCP Business Tools. For a narrow inventory/order-preparation scope it is defensible, but the surface feels underdeveloped.
The surface covers search and order proposal preparation only. It lacks order commitment, inventory detail retrieval, stock mutation, order lifecycle operations, and other basic business workflow tools, creating significant dead ends.