A simple MCP server that provides greeting and code review prompt capabilities
The greeter server has exactly 1 tool (greet) with a minimal but complete schema. However, the tool definition exhibits several quality gaps that prevent a higher score: (1) The tool name 'greet' lacks a clear action verb prefix, it should be 'send_greeting' or 'greet_user' to follow the verb_noun convention. (2) The description 'say hi' is trivial (6 chars) and does not explain when or why to use the tool, falling far below the 10 - 1024 char baseline and the 50 - 200 char LLM-optimized range. (3) The input parameter 'name' has a description ('the name of the person to greet') that is present but minimal, it does not clarify format expectations or constraints. (4) There is no documented output schema; the response structure is inferred from the code (TextContent with a greeting string) but not formally declared. (5) No error handling is visible, what happens if 'name' is empty, null, or contains injection attempts? The tool is READ_ONLY (correct risk classification), but lacks the robustness expected of production-grade tools. The tool is directly visible in main.go and properly registered via mcp.AddTool(), so inference is not an issue.
say hi
Tool name 'greet' does not follow verb_noun convention. Should start with action verb (e.g. 'send_greeting', 'greet_user') for LLM clarity.
Tool description 'say hi' is only 6 characters, far below the 10 - 1024 character baseline and the LLM-optimized 50 - 200 character range. Does not explain what the tool does, when to use it, or what it returns.
Output schema is not documented. The response structure (greeting string wrapped in TextContent) must be formally declared so LLMs know what fields to expect.
No error handling visible. Tool does not validate input (empty name, null, injection attempts) or provide recovery guidance if operation fails.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 47 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 33 | - | v1 |
Parameter 'name' description is minimal ('the name of the person to greet'). Does not clarify format, length constraints, or character restrictions.