MCP Tool Auditor

audit_tool_list

Audit an entire tool list in one pass. Detect overcrowding, rank tools by quality score, and identify worst offenders to improve model accuracy.

Instructions

Audit an entire list of tools at once. Detects overcrowding (too many tools hurt accuracy), ranks each tool by quality score, and flags the worst offenders. Research shows accuracy drops below 90% when weaker models see more than 10-15 tools.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tools": "<tools>"
    },
    "name": "audit_tool_list"
  }
}

Input Schema

Name	Required	Description	Default
`tools`	Yes	Array of tool objects to audit

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden. It goes beyond a simple statement of action by explaining the logic behind the tool: detecting overcrowding with a specific research-based accuracy threshold and ranking/flags. This provides meaningful context about what the tool does and why, though it does not delve into edge cases or exact output formatting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core purpose, and each sentence adds value. The second sentence provides supporting evidence for the 'overcrowding' check, making the description both informative and concise without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with a single parameter and no annotations, the description is reasonably complete: it explains what the tool does, why (research-based threshold), and what outputs to expect (ranking, flags). However, without an output schema, it could be more explicit about the exact structure of the returned data, but the description's mention of ranking and flags covers the essentials.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes the only parameter ('tools') as 'Array of tool objects to audit,' which provides 100% coverage. The tool description does not add additional parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb and resource: 'Audit an entire list of tools at once.' It distinguishes itself from sibling 'audit_tool' by emphasizing the batch aspect, and enumerates key capabilities (detect overcrowding, rank by quality score, flag worst offenders).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes it clear this tool is for auditing a list of tools (batch processing), which gives a clear usage context. However, it does not explicitly mention alternatives or exclusion criteria, such as 'for a single tool, use audit_tool instead.' The context is clear but lacks explicit differentiation from sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server