Skip to main content
Glama

mcp_diet_analyze_tools

Read-onlyIdempotent

Analyze MCP tool definitions to estimate byte and token savings from tree-shaking policies before applying filters, helping you decide which tools to keep.

Instructions

Analyze an array of MCP tool definitions and compute deterministic tree-shaking byte and token savings under mcp-diet policies.

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": "mcp_diet_analyze_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolsYesArray of MCP tool definition objects to analyze.
readOnlyNoKeep only read-only tools.
maxDescCharsNoMaximum description length in characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world behavior, so the safety profile is covered. The description adds genuinely useful context by calling the computation 'deterministic,' which tells the agent results are reproducible. It still omits what the computed savings look like (structure, units, whether estimates or exact counts), which matters for a pure-analysis tool.

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

Conciseness4/5

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

A single dense sentence with the resource and the computed result front-loaded; nothing is redundant. It leans on internal jargon ('tree-shaking,' 'mcp-diet policies') that costs clarity slightly but not length.

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

Completeness3/5

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

No output schema exists, so the description should describe the return shape; it only says it 'computes savings' without indicating format, fields, or whether per-tool breakdowns are returned. Combined with 100% schema coverage on inputs, it is adequate but leaves the agent guessing about results.

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?

Schema description coverage is 100%, so all three parameters (tools, readOnly, maxDescChars) are already documented in the schema. The description adds nothing about how the policy filters interact with the analysis or what defaults apply, so the baseline 3 is appropriate.

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

Purpose4/5

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

Uses a specific verb (Analyze) plus a clearly delimited resource (an array of MCP tool definitions) and states the output it computes: deterministic tree-shaking byte and token savings. An agent can grasp the function immediately, though it never contrasts itself with the siblings (read_spill, redact_text, status), which the byte/token framing only implicitly distinguishes from.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no prerequisites or conditions under which the analysis should be run. The phrase 'under mcp-diet policies' hints at context but never tells the agent when to reach for this tool instead of redact_text or status.

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