Loading ToolBench

Reading the current corpus…

Anvil MCP server · F · ToolBench

Anvil

Anvil is a distributed workflow orchestration platform with edge Worker support. It provides MCP (Model Context Protocol) integration for tool execution through stdio-based MCP servers. The server manages artifacts, pipelines, materials, hooks, and nodes with support for both in-process and NATS-based distributed modes.

2026-07-28+STDIO3 tools

32/100

Definition Quality27

Protocol Readiness35

Supportability38

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Anvil MCP server has severe definition quality gaps. Only 3 tools are exposed, all with minimal descriptions. The 'initialize', 'tools/list', and 'tools/call' tools are framework-level meta-tools, not domain tools. 'tools/call' has a schema but lacks parameter descriptions. Descriptions are under 100 chars and lack actionable context. No error recovery guidance. No tool annotations (readOnlyHint/destructiveHint). The server appears to be a generic MCP framework rather than a domain-specific tool collection.

Tools (3)

initializeread only28/100

MCP protocol initialization handshake. Returns protocol version, server capabilities, and server info.

tools/callwrite45/100

Executes a registered tool by name with provided arguments. Returns tool execution result as text content.

tools/listread only28/100

Lists all available tools registered with the MCP server. Returns tool name, description, and input schema for each tool.

Issues (5)

CRITICALtool ↗

No input schemas for 'initialize' and 'tools/list'.

initializetools/list

CRITICALtool-description ↗

Parameter descriptions missing. 'tools/call' has 'name' and 'arguments' params with minimal descriptions ('Name of the tool to execute', 'Tool-specific arguments'). LLMs cannot infer parameter semantics from these generic labels.

tools/call

HIGHtool-description ↗

Tool descriptions are under 100 chars and lack context. 'MCP protocol initialization handshake' does not explain WHEN to call it or WHAT it returns in actionable terms for an LLM.

initializetools/list

HIGHtool-annotations ↗

No tool annotations. 'initialize' and 'tools/list' are read-only; 'tools/call' is destructive. Missing readOnlyHint and destructiveHint annotations per current MCP spec (2026-07-28).

initializetools/listtools/call

Recommendations

Add explicit input schemas to 'initialize' and 'tools/list' (even if empty objects). Document expected output structure (protocolVersion, capabilities, serverInfo fields).
Expand parameter descriptions for 'tools/call': 'name' should be 'The unique identifier of the registered tool to invoke (string, case-sensitive)'; 'arguments' should be 'A JSON object containing tool-specific parameters. Structure depends on the tool's inputSchema.'
Add tool annotations to the ToolDef struct: readOnlyHint=true for 'initialize' and 'tools/list'; destructiveHint=true for 'tools/call' (since it executes arbitrary handlers).
Enhance error messages with recovery hints: 'Tool "xyz" not found. Call tools/list to see available tools.' Include available tool names in the error response.
Document output schemas for all tools. E.g., 'initialize returns {protocolVersion: string, capabilities: object, serverInfo: {name, version}}'. Add this to tool descriptions or a separate schema field.

Score history

Overall score trend

First recorded score · v2 rubric

32/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	32	2026-07-28+	v2