Loading ToolBench
A zero-dependency Model Context Protocol server for two-go, a fluent HTTP/API testing library. Provides tools for making HTTP requests, generating test suites from API definitions (OpenAPI, Postman), and validating JSON schemas.
Two-go MCP server has 5 tools with explicit registration and schemas visible in src/mcp/server.js. Tool definitions are present and mostly well-structured, but descriptions lack the depth and specificity required for robust LLM decision-making. Most parameter descriptions are minimal or absent. Output schemas are not documented. Error handling guidance is minimal. This server lands in the 'fair to poor' range typical of community tools, it works but lacks the polish required for production agent systems. Transport is STDIO-only, which is a hard architectural limitation.
Generate a two-go test suite source from an OpenAPI 3 document.
Generate a two-go test suite source from a Postman v2.1 collection.
Send an HTTP request and return status, headers, timing and body.
Infer a JSON schema from an example value.
Validate a value against a JSON schema. Returns { valid, errors }.
Missing output schema documentation for all tools. LLMs cannot plan downstream tool calls without knowing what fields to expect.
Parameter descriptions missing or inadequate. 'spec' in gen_openapi/gen_postman has no description. 'value' in infer_schema/validate_schema lacks context on expected types or formats. LLMs cannot infer meaning from names alone.
Tool descriptions too brief (10-50 chars). gen_openapi, gen_postman, infer_schema, validate_schema lack 'when to use' guidance and dependency hints. Descriptions should be 50-200 chars to guide LLM selection.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
No error handling guidance. Tools return raw errors without recovery suggestions. E.g., when http_request fails with 404 or network error, the LLM has no actionable next step.
http_request lacks enum constraint on 'method' parameter. Free-form string invites hallucinated HTTP verbs (e.g., 'GRAB', 'FETCH'). Should declare enum: ['GET', 'POST', 'PUT', 'PATCH', 'DELETE', 'HEAD', 'OPTIONS'].
No input validation errors or guidance. Tool definitions do not indicate which parameters are required beyond JSON Schema 'required' array, or what formats/ranges are acceptable.
STDIO transport only. Server cannot be accessed by hosted MCP clients, limiting deployment options to local/direct invocation. Hard architectural ceiling.