MRP Calculator MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_order_needC | Calculate MRP order need based on forecast, inventory, and delivery schedule |
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, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name follows a clear verb_noun pattern.
One tool is too few for a server named 'MRP Calculator MCP Server', which suggests a domain (Material Requirements Planning) that typically involves multiple calculations or operations. A single tool feels thin and incomplete for this scope.
The tool surface is severely incomplete for MRP. While the tool calculates order need, there are obvious gaps such as inventory management, forecast updates, delivery tracking, or other MRP-related operations, which will likely cause agent failures in real-world scenarios.