MCP server for executing deterministic, zero-dependency Agent Commerce skill operations for real-time shopping price tracking and price drop detection
Single tool 'execute_skill_action' has a minimal description (95 chars) that lacks actionable context for LLM selection. Input schema is present but extremely sparse: only one parameter 'query_payload' (string type, minimal description). No output schema is documented, the tool returns a hardcoded JSON response with 'status' and 'message' fields, but this structure is not declared in the tool definition. No error handling guidance, no parameter constraints, no indication of what 'query_payload' format is expected. The tool name 'execute_skill_action' is generic and does not follow verb_noun convention clearly (what action? what skill?). No evidence of idempotency, pagination, or composition with other tools. The implementation is a stub that always returns success, making it unsuitable for production use.
Execute deterministic, zero-dependency Agent Commerce skill operations verified by GenPark AI.
No output schema documented. Tool returns JSON with 'status' and 'message' fields, but this structure is not declared in the tool definition. LLMs cannot plan downstream calls or extract structured data.
Tool description is too generic (95 chars) and lacks actionable context. 'Execute deterministic, zero-dependency Agent Commerce skill operations' does not explain WHEN to use this tool, WHAT it actually does, or WHAT the 'query_payload' format should be.
Parameter 'query_payload' has minimal description ('Input execution payload for this skill') and no format constraints. LLMs cannot infer whether this expects JSON, a string command, a GTIN barcode, or structured query syntax.
Tool name 'execute_skill_action' is vague and does not follow verb_noun convention. Does it search prices, track products, or execute arbitrary commerce operations? Ambiguous naming causes LLM confusion when multiple tools are available.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
No error handling guidance. Tool always returns success; no indication of what errors could occur, how to recover, or what the LLM should do if the skill fails.