MCP server for Retail Reason, a product for Walmart suppliers providing advisory and workspace management capabilities
Critical gaps across all dimensions. Descriptions are present but minimal (45-50 chars, below 20-char floor for scoring). No parameter documentation, no output schema specification, no error handling guidance. Tool names follow verb_noun pattern (list_, get_) but lack context for LLM selection. No evidence of pagination, field typing, or composition support. This server exposes raw API surface with minimal agent-optimization.
Get capabilities available for a specific workspace
List available workspaces for the authenticated user
No input schemas visible for either tool. Cannot verify parameter types, constraints, or descriptions.
Descriptions lack WHAT/WHEN/WHY context. 'List available workspaces' does not explain when to call this vs alternatives, what structure is returned, or prerequisites.
No output schema documented. LLM cannot infer what fields list_workspaces returns (workspace_id? name? metadata?). Cannot plan downstream tool calls or extract required data.
No parameter documentation visible. get_capabilities likely requires a workspace_id parameter, but no description explains format, constraints, or whether it accepts names vs IDs.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 37 | 2026-07-28+ | v2 |
No error handling guidance. No recovery hints, retryability classification, or actionable error messages. LLM cannot self-correct on invalid workspace_id or permission failures.