MCP server for a sales/order management assistant in the metallurgical transformation industry. Provides tools for managing orders, clients, stock, deliveries, and complaints.
Critical gaps across all dimensions. Tool definitions are inferred from file paths and brief descriptions only, no explicit schema definitions visible in source. Descriptions are generic (10-50 chars) and lack actionable context. No parameter schemas, types, or constraints documented. No error handling guidance. No output schema documentation. Tool names lack action verbs (e.g., 'orders' vs 'list_orders' or 'get_orders'). This server cannot be reliably used by LLMs without substantial schema and documentation work.
Tool for managing and querying client/customer information
Tool for managing and querying delivery information and estimates
Tool for managing and querying order information
Tool for managing and querying customer complaints and claims
Tool for querying inventory and stock levels
No input schemas visible. Tool definitions inferred from file paths only. Cannot verify parameter types, constraints, or required fields.
Tool names lack action verbs. 'orders', 'clients', 'stock' are nouns, not verbs. LLMs cannot infer intent from names alone. Should be 'list_orders', 'get_clients', 'query_stock', etc.
Descriptions are generic and under 50 characters. 'Tool for managing and querying order information' does not explain WHEN to use this tool vs others, what it returns, or what parameters it accepts. Descriptions must be 50-200 chars and answer: what, when, what returns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 24 | 2026-07-28+ | v2 |
No parameter documentation visible. Cannot verify if tools accept filters, pagination, sorting, or required identifiers. LLMs will guess at parameter names and types, causing failures.
No output schema documentation. LLMs cannot plan downstream tool calls or extract required fields (e.g., order_id, client_id) for chaining. Responses are opaque.