Loading ToolBench

Reading the current corpus…

mcp-typescript-server-examples MCP server · D · ToolBench

← Browse

mcp-typescript-server-examples

github.com/mikelovesrobots/mcp-typescript-server-examples

Just running a sample mcp server

2025-06-18+STREAMABLE_HTTP1 tools

54/100

Definition Quality57

Protocol Readiness75

Supportability36

Spec posture

Inferred effective spec 2025-06-18+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: structured output, Streamable HTTP

No deprecated protocol patterns detected

Summary

Single tool with basic structure but significant gaps in parameter documentation and output schema clarity. Output schema is present in code but not documented for the LLM. Description is adequate but generic. Overall fits the 'poor to fair' range (D/C boundary).

Tools (1)

roll-diceread onlysource verified57/100

Rolls dice and returns the result

Issues (5)

CRITICALtool-description ↗

Parameter 'diceSides' has null description, LLMs cannot infer what values are valid or expected

roll-dice

HIGHconstrained-input ↗

Input schema uses Zod validation (z.number()) but does not declare numeric range constraints (min/max), LLMs may pass absurd values (0, negative, or extremely large numbers)

roll-dice

HIGHtool ↗

Output schema is defined in code but not documented in the tool registration for the LLM, LLMs do not have visibility into the expected response structure (rollResult: number)

roll-dice

HIGHparam-validation-rules ↗

Tool description does not specify what range of values is valid (e.g., 'diceSides must be 1-100') or clarify the return type

roll-dice

LOWtool ↗

Tool name 'roll-dice' is acceptable but lacks a clear verb-noun structure; 'roll_dice' or 'roll_d_sides' would be more conventional

Recommendations

Add a non-empty description to the 'diceSides' parameter: e.g., 'Number of sides on the die (1-100). Common values: 6 (standard die), 20 (d20 in tabletop gaming), 100 (percentile die).'
Declare min and max constraints on the diceSides parameter in the schema: z.number().min(1).max(100) instead of bare z.number().
Document the output schema in the tool description: 'Returns an object with rollResult (integer between 1 and diceSides inclusive).'
Expand the tool description to clarify when to use it and what it returns: 'Simulates rolling a multi-sided die. Pass the number of sides (e.g., 6, 20, 100) and receive a random integer result. Useful for randomization, gaming, or decision-making when outcomes must be unpredictable.'
Consider renaming to 'roll_d_sides' or 'roll_sided_dice' to follow verb_noun convention more explicitly.

Score history

Overall score trend

↑ 17 points across a rubric change (v1 → v2)

54/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-22	D	54	2025-06-18+	v2
2026-03-09	F	37	-	v1