Skip to main content
Glama

tidy

Generates proposals for duplicate rules, rules not cited lately, core budget concerns, and coverage gaps; changes are not applied.

Instructions

The rules clerk's proposals (duplicates, rules not cited lately, core budget, gaps). Proposals only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key trait: output is proposals, not applied changes, implying a non-mutating read. That is a real safety-relevant disclosure. However, it says nothing about whether proposals are computed fresh per call, whether they are stored, cost/latency, or any permission requirement.

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

Conciseness3/5

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

Two short fragments with no filler, which is appropriately sized for a simple tool. But the telegraphic style hurts more than it helps: 'core budget' and 'gaps' are unexplained jargon, and the key claim ('proposals only') is buried after the parenthetical list rather than front-loaded.

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?

The tool is simple (no params, output schema present so return shape is covered), and the description explains what the proposals concern. It falls short on naming the actor 'the rules clerk' and on glossing opaque categories like 'core budget' and 'gaps', leaving an agent unable to judge when this tool is the right first move.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No parameter information is missing.

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

Purpose3/5

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

The description identifies the resource as 'the rules clerk's proposals' and enumerates their categories (duplicates, uncited rules, core budget, gaps), but never states a verb — an agent cannot tell whether this generates, recomputes, or merely lists existing proposals. 'Proposals only' is the closest thing to a defining action. It does implicitly separate the tool from siblings like rule_add by framing output as suggestions rather than applied change, but only implicitly.

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?

'Proposals only' is a weak usage constraint hinting that this tool does not mutate the ruleset, but the description never says when to call it, what precondition (e.g. after rule changes) triggers it, or which sibling to use instead to actually apply a proposal. No alternatives are named and no exclusions are stated beyond the terse 'only'.

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

Deploy Server

Other Tools