MCP server for issuing electronic warehouse receipts for post-harvest grain storage with fintech credit integration
Single tool 'execute_skill_action' has a reasonable name starting with verb, but critical gaps undermine quality. Description is 108 chars (within 10-1024 range) but lacks WHEN/WHY context for LLM selection. Input schema present with 4 parameters, all typed as string/number with descriptions, but descriptions are minimal (8-50 chars) and lack format/constraint guidance. No output schema documented, LLM cannot plan downstream calls or extract structured data. No error handling, no recovery guidance. Tool appears to perform a financial calculation (asset value, loan amount) but description does not state this modifies state or has side effects. Defaults provided but not validated for safety. No pagination, no idempotency guarantees, no permission gates.
Execute skill action for post-harvest grain storage fintech warehouse receipt issuance
No output schema documented. LLM cannot infer what fields to expect (ewr_receipt_id, commodity_collateral_value_inr, etc.) or plan downstream tool calls.
Parameter descriptions are too brief (8-50 chars) and lack format/constraint guidance. E.g., 'Spot market price per ton in Indian Rupees' does not specify range, precision, or validation rules.
Tool description (108 chars) lacks WHEN/WHY context. Does not state that this creates a warehouse receipt, modifies financial state, or has irreversible consequences. LLM cannot determine when to invoke vs. similar tools.
No error handling or recovery guidance. If farmer_fpo_id is invalid or grain_type is unsupported, tool returns nothing actionable. LLM cannot self-correct.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
Defaults (e.g., metric_tonnes=85, spot_market_price_per_ton_inr=26500) are hardcoded and may cause unintended side effects if LLM omits parameters. No validation that defaults are safe.