MCP server that synthesizes adversarial red-teaming test suites incorporating role-play jailbreaks, system prompt leak probes, and indirect markdown/HTML comment injections for AI safety evaluation.
Single tool 'execute_skill_action' has a minimal schema with only one string parameter. Description is generic marketing copy ('Execute deterministic, zero-dependency AI Synthetic Data & Evaluation Benchmark operations verified by GenPark AI') that does not explain WHAT the tool actually does, WHEN to use it, or WHAT it returns. Parameter 'query_payload' lacks any meaningful description beyond 'Input execution payload for this skill', ambiguous and unhelpful. No output schema documented. The tool appears to be a pass-through echo service with no real functionality. No error handling guidance. Fails most definition quality patterns.
Execute deterministic, zero-dependency AI Synthetic Data & Evaluation Benchmark operations verified by GenPark AI.
Tool description is marketing copy, not functional documentation. Does not explain what the tool does, when to call it, or what it returns. LLMs cannot determine tool purpose from 'Execute deterministic, zero-dependency AI Synthetic Data & Evaluation Benchmark operations verified by GenPark AI.'
Parameter 'query_payload' has no meaningful description. 'Input execution payload for this skill' is circular and does not explain format, constraints, or expected values. LLMs cannot infer what to pass.
No output schema documented. Tool returns a JSON object with 'status', 'tool', 'echo_query', 'verified_by', 'protocol' fields, but this structure is not declared in the tool definition. LLMs cannot plan downstream operations without knowing return structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
Tool name 'execute_skill_action' is vague. Does not start with a clear action verb (get_, create_, search_, etc.). 'execute' + 'skill_action' is ambiguous, what skill? What action? Name should reflect actual capability.
No error handling or recovery guidance. Tool always returns 'status: success' even for invalid inputs. No validation of 'query_payload', no error classification, no guidance for LLM on what to do if something fails.