Loading ToolBench

Reading the current corpus…

dockerized-mcp-server-template MCP server · F · ToolBench

dockerized-mcp-server-template

github.com/nealriley/dockerized-mcp-server-template

A template MCP server that dynamically generates tools from an OpenAPI specification and exposes them via FastMCP with SSE transport. Designed to be containerized and deployed with Docker.

<=2025-11-25STREAMABLE_HTTP1 tools

25/100

Definition Quality10

Protocol Readiness62

SupportabilityNot measured-

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

Single tool 'dynamic_openapi_tools' has critical definition gaps. Tool name lacks action verb (should be 'call_openapi_endpoint' or similar). Description is generic and does not explain WHEN to use this tool vs calling endpoints directly. Input schema shows three top-level params (path_parameters, query_parameters, body) but lacks per-parameter type definitions, descriptions, and constraints. No output schema documented. No error handling guidance. Tool is dynamically generated from OpenAPI spec, making static validation impossible, actual tool names, descriptions, and schemas are runtime-generated and not visible in source code.

Tools (1)

dynamic_openapi_toolswriteauth13/100

Dynamically generated tools from OpenAPI specification paths. Each path and method in the OpenAPI spec becomes a tool with the naming pattern: {TOOL_PREFIX}_{method}_{path}. Tools forward HTTP requests to the base URL specified in the OpenAPI spec with appropriate headers (x-api-key, version, unique-key) and parameters.

Issues (5)

CRITICALtool ↗

Tool definition is dynamically generated at runtime; actual tool names, descriptions, input/output schemas are not visible in source code.

dynamic_openapi_tools

CRITICALconstrained-input ↗

Input schema lacks per-parameter type definitions and descriptions. Schema shows three top-level object properties (path_parameters, query_parameters, body) but does not specify types (string, number, boolean, object), constraints (enum, pattern, minLength), or descriptions for each parameter.

dynamic_openapi_tools

CRITICALtool ↗

No output schema documented. Tool description does not specify what fields the response contains, their types, or structure. LLMs cannot plan downstream tool calls or extract data without knowing response shape. LLMs need to know what fields to expect.'

dynamic_openapi_tools

Recommendations

Rename tool to start with action verb: 'call_openapi_endpoint' or 'invoke_api_method'. This helps LLMs infer intent from the name alone.
Expand tool description to 50 - 200 characters explaining: (1) what it does (forwards HTTP requests to OpenAPI endpoints), (2) when to use it (when you need to call an external API), (3) what it returns (the API response as JSON). Current description is too generic.
Add per-parameter descriptions in the input schema. For 'path_parameters': 'Object with path variables extracted from the OpenAPI spec (e.g., {id}, {resource_id}). Keys are parameter names, values are strings or numbers.' For 'query_parameters': 'Object with query string parameters. Keys are parameter names, values are strings or numbers.' For 'body': 'Request body for POST/PUT/PATCH operations. Must be a valid JSON object matching the OpenAPI spec schema.'
Document output schema in tool description: 'Returns the API response as a JSON object. Structure depends on the OpenAPI endpoint. Common fields: status (HTTP status code), data (response body), error (error message if request failed).'
Add error handling guidance: 'If the API returns a 4xx error, the request parameters are invalid, check path_parameters, query_parameters, and body against the OpenAPI spec. If 5xx, the API is unavailable, retry after a delay. If connection fails, the base URL may be unreachable.'

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

25/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	25	<=2025-11-25	v2