Loading ToolBench

Reading the current corpus…

zcode-jetbrains-plugin MCP server · F · ToolBench

← Browse

zcode-jetbrains-plugin

github.com/csuftt/zcode-jetbrains-plugin

JetBrains IDE plugin for ZCode with MCP server integration, webview UI, and tool management

<=2025-11-25STDIO1 tools

32/100

Definition Quality26

Protocol Readiness47

SupportabilityNot measured-

Spec posture

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

Static source inference · medium confidence · detected: stateful session

Deprecated protocol patterns detected

Summary

Single tool 'listTools' with severely deficient definition. Description is 127 chars but vague, does not explain WHEN to use it or what it returns. Input schema present but lacks proper type definitions for nested 'server' object (should specify McpServerInfo structure). No output schema documented. Tool appears to be a meta-tool for discovering MCP servers rather than a domain-specific capability. No error handling guidance. Naming is generic ('listTools' vs verb_noun pattern 'list_mcp_tools'). This is a discovery/introspection tool, not a production agent capability.

Tools (1)

listToolsread only33/100

Connect to MCP server and retrieve tools list via JSON-RPC protocol (supports both stdio and HTTP/SSE transports)

Issues (5)

CRITICALtool ↗

Missing output schema documentation. Tool description does not specify what fields are returned (e.g., tool names, descriptions, parameter schemas). LLMs cannot plan downstream calls without knowing the response structure.

listTools

CRITICALconstrained-input ↗

Input parameter 'server' has type 'object' but no nested schema. McpServerInfo structure is not defined, LLMs cannot determine what fields (host, port, command, env, etc.) are required or optional.

listTools

HIGHtool-description ↗

Description is vague and does not explain WHEN to call this tool or what problem it solves. 'Connect to MCP server and retrieve tools list' lacks context for LLM selection. Does not state whether this is for discovery, validation, or integration.

listTools

MEDIUMtool ↗

Tool name 'listTools' violates verb_noun convention. Should be 'list_mcp_tools' or 'list_remote_tools' to match LLM parsing expectations and disambiguate from other list operations.

Recommendations

Document the complete output schema: return type (array of tools), each tool object structure (name, description, inputSchema, risk), and total count. Example: {tools: [{name: string, description: string, inputSchema: object}], total: number}
Expand input schema for 'server' parameter: define McpServerInfo as a proper object schema with required fields (command or url), optional fields (env, args, timeout), and descriptions for each.
Rewrite description to 50-100 chars explaining purpose: 'Discover available tools from a remote MCP server. Call this first to see what capabilities are exposed before invoking them.'
Rename tool to 'list_mcp_tools' to follow verb_noun convention and improve LLM parsing.
Add error handling guidance: 'If connection fails, verify server is running and accessible. If timeout occurs, increase timeoutMs parameter (default 45000ms).'

Spec posture evidence

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

Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained

Score history

Overall score trend

First recorded score · v2 rubric

32/100

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