Loading ToolBench

Reading the current corpus…

hello-gomcp MCP server · F · ToolBench

← Browse

hello-gomcp

github.com/bioerrorlog/hello-gomcp

A minimal MCP server implementation in Go demonstrating tools, resources, and prompts

2026-07-28+STDIO1 tools

35/100

Definition Quality45

Protocol Readiness28

Supportability23

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Single tool 'add' has a basic description but critical gaps in parameter documentation. Parameter descriptions are null/missing (violates pattern:tool-description baseline of 100% A+ tools having param descriptions). No output schema documented. Tool naming is acceptable but minimal. No error handling guidance. STDIO transport caps overall potential.

Tools (1)

addread onlysource verified45/100

Add two numbers

Issues (5)

CRITICALpattern:tool-description ↗

Parameter descriptions are null/missing for 'x' and 'y'. Rubric baseline: 100% of A+ tool params have descriptions. LLMs cannot infer that 'x' and 'y' are operands without explicit text.

add

CRITICALpattern:tool ↗

No output schema documented. Tool returns text via mcp.NewToolResultText() but LLMs have no visibility into the response structure (e.g., is it a number string, formatted decimal, error message?). Rubric baseline: 100% of A+ tools have documented return types.

add

HIGHpattern:recovery-guide ↗

No error handling or recovery guidance. If addition fails or inputs are invalid, addToolHandler returns a generic error with no actionable next steps for the LLM. Rubric baseline: error responses must guide recovery.

add

HIGHprotocol:transport ↗

STDIO-only transport. Not remotely accessible; cannot be used by hosted MCP clients.

Recommendations

Add explicit descriptions to 'x' and 'y' parameters: e.g., 'x: The first number to add (numeric value)' and 'y: The second number to add (numeric value)'.
Document the output schema in the tool description: 'Returns the sum as a decimal string formatted to 2 decimal places (e.g., "42.50")'.
Add numeric constraints to parameter descriptions: 'x: First operand (numeric, range: -1e308 to 1e308)' or document any practical limits.
Implement input validation in addToolHandler with actionable error messages: 'Invalid input: x and y must be numbers. Got x={type(x)}, y={type(y)}'.
Migrate from STDIO to HTTP+SSE or Streamable HTTP transport to enable remote client access and improve protocolReadiness score.

Score history

Overall score trend

First recorded score · v2 rubric

35/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	35	2026-07-28+	v2