MCP server that provides tools for adding numbers and creating posts on Twitter/X
Both tools have minimal descriptions (under 50 chars) and parameter descriptions are entirely missing (null). Schemas are present with proper types (number, string) but lack parameter-level documentation. Tool naming is acceptable but descriptions fail to explain WHEN to use each tool or what they return. No error handling guidance, no output schema documentation, and no indication of side effects for the destructive createPost tool. This server falls well below production baseline (194 char avg description, 100% param annotation in A+ tools).
Add two numbers
Create a post on X formally known as Twitter
All parameter descriptions are null. Parameters 'a', 'b', and 'status' lack any documentation explaining their purpose, format, or constraints.
Tool descriptions are too short (<50 chars) and lack context. 'Add two numbers' does not explain when to use this vs other math tools. 'Create a post on X formally known as Twitter' does not document that this is a destructive, irreversible operation or what the return value contains.
No output schema documented. LLMs cannot plan downstream calls or extract fields from responses. The createPost tool returns {content: [{type, text}]} but this structure is not declared in the tool definition.
createPost is a destructive operation (WRITE risk) but has no confirmation step, dry-run option, or error recovery guidance. Agents may post unintended content without safeguards.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If Twitter API fails, the LLM receives no actionable error message or retry strategy.