Loading ToolBench

Reading the current corpus…

openapi-mcp-server MCP server · F · ToolBench

openapi-mcp-server

github.com/h2562961224/openapi-mcp-server

An MCP server that dynamically exposes REST API endpoints from a Spring Boot application as MCP tools by parsing OpenAPI specifications

<=2025-11-25STREAMABLE_HTTP1 tools

22/100

Definition Quality14

Protocol Readiness42

Supportability23

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_rest_api_tools' has critical definition gaps. Tool name is generic and does not follow verb_noun pattern (should be 'call_rest_endpoint' or similar). Description is present but vague, it describes the mechanism (dynamically generated from OpenAPI) rather than what the LLM should do with it. Input schema is declared as a string ('JSON.toJSONString(schema)') rather than a proper structured JSON Schema object, making it unparseable by MCP clients. No output schema is documented. No parameter descriptions beyond the generic 'Input schema is dynamically determined'. Error handling returns raw exception messages ('Error: ' + e.getMessage()) without recovery guidance. The tool conflates multiple concerns: endpoint discovery, parameter marshalling, invocation, and result serialization.

Tools (1)

dynamic_rest_api_toolswriteauth17/100

Dynamically generated tools from Spring Boot REST API endpoints. Each endpoint is converted to an MCP tool with the tool name derived from the controller class and method name, description from OpenAPI tags and operation description, and input schema from the request body schema.

Issues (5)

CRITICALtool ↗

Input schema is serialized as a JSON string, not a structured JSON Schema object. MCP clients cannot parse or validate it. Line: JSON.toJSONString(schema) in RestApiToolProvider.java.

dynamic_rest_api_tools

CRITICALtool ↗

Tool name 'dynamic_rest_api_tools' is generic and does not start with an action verb. Should be 'call_rest_endpoint', 'invoke_api_method', or similar to signal intent to the LLM.

dynamic_rest_api_tools

CRITICALtool ↗

No output schema documented. LLMs cannot predict what fields the tool returns, breaking downstream tool chaining and forcing exploratory calls.

dynamic_rest_api_tools

HIGHrecovery-guide ↗

Error responses return raw exception messages ('Error: ' + e.getMessage()) without recovery guidance. LLM cannot determine if error is retryable, user-fixable, or fatal.

dynamic_rest_api_tools

Recommendations

Replace JSON.toJSONString(schema) with a proper McpSchema.Tool input schema object. Parse the OpenAPI schema into a structured JSON Schema with type, properties, required, and descriptions for each field.
Rename tool to 'invoke_rest_api' or 'call_api_endpoint' to signal action intent. Add a description: 'Invoke a Spring Boot REST API endpoint. Provide the endpoint path and request body matching the OpenAPI schema. Returns the endpoint response as JSON.'
Document the output schema in the tool definition. Specify that the response is a JSON object with the structure defined by the endpoint's OpenAPI response schema.
Enhance error handling to categorize failures: return 'Retryable: Connection timeout. Retry in 5 seconds.' for transient errors, 'User-fixable: Invalid request body. Expected fields: [list]. Got: [actual].' for validation errors, and 'Fatal: Endpoint not found.' for permanent failures.
Add parameter descriptions for dynamically generated fields. For each OpenAPI request body property, include its type, constraints, and whether it is required. Example: 'user_id (string, required): The unique identifier of the user to update.'

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

22/100

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