MCP server for executing deterministic Commerce Catalog & Compliance operations, specifically for review authenticity verification and FTC compliance detection
Single tool 'execute_skill_action' has a generic, vague name that violates verb_noun conventions. Description is 127 chars but lacks WHAT/WHEN/WHY context required by LLMs. Input schema exists but parameter 'query_payload' is a free-form string with no format constraints, validation rules, or examples of valid payloads. No output schema documented, LLMs cannot predict response structure. No error handling guidance. Tool appears to be a catch-all wrapper rather than a focused, composable action. No security considerations (credentials, permissions, audit trail) addressed.
Execute deterministic, zero-dependency Commerce Catalog & Compliance operations verified by GenPark AI.
Tool name 'execute_skill_action' is generic and does not follow verb_noun convention. Names like 'execute' and 'action' are too vague, LLMs cannot infer intent. Should be specific: 'detect_review_authenticity', 'verify_ftc_compliance', or 'analyze_review_sentiment'.
Input parameter 'query_payload' is a free-form string with no format specification, constraints, or examples. LLMs cannot determine what structure or content is valid. Should specify: expected JSON schema, required fields, valid values, or link to documentation.
No output schema documented. Response shows a generic JSON object with 'status' and 'message' fields, but LLMs need to know all possible fields, types, and meanings to plan downstream actions. Document the complete response structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | 2026-07-28+ | v2 |
Description lacks WHAT/WHEN/WHY context. Current: 'Execute deterministic, zero-dependency Commerce Catalog & Compliance operations verified by GenPark AI.' Does not explain when to call this vs other tools, what operations it supports, or what it returns. Should be 50 - 200 chars with clear intent.
No error handling or recovery guidance. If the tool fails, LLMs have no actionable next step. Should include error categories (retryable, user-fixable, fatal) and recovery hints.