Loading ToolBench
Unified MCP Streamable HTTP 2025-11-25 transport, OAuth 2.1 AS, lifecycle, install
Single tool 'config__open_relay' has critical definition gaps. Input schema is empty object {} with no parameters documented. Description is present (89 chars) but lacks actionable detail on when/why to use it, what it returns, or error cases. No parameter descriptions exist (N/A due to empty schema). Output schema is not documented in source. Tool name uses double underscore (non-standard verb_noun convention) and is unclear, 'config' is not an action verb. No evidence of error handling, validation, or recovery guidance. Fails multiple hard scoring rules: empty input schema (schema=0), minimal description context (description capped at 40), and inferred tool definition from file path only (overall capped at 50).
Get the relay configuration URL for {server_name}, opening it in the user's browser when possible. Returns the relay URL, whether the browser launched, and the current status.
Empty input schema: tool accepts {} with no parameters. Tool definition inferred from file path, not explicit registration visible in source.
Tool name 'config__open_relay' violates verb_noun convention. Does not start with action verb (get_, open_, fetch_, etc.). Double underscore is non-standard. LLM cannot infer intent from name alone.
Description (89 chars) lacks WHAT/WHEN/WHY context. States 'Get the relay configuration URL' and 'opening it in the user's browser' but does not explain when to call this tool, what prerequisites exist, or what the return value structure is. No output schema documented.
No error handling or recovery guidance. Description does not address: What if browser launch fails? What if relay URL is unavailable? What does 'current status' mean? LLM has no guidance on next steps if tool fails.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
Parameter 'server_name' is referenced in description but not declared in input schema. Schema is empty {}. This is a critical mismatch, either schema is incomplete or description is wrong.