Skip to main content
Glama

pare_debt

Scans repository files for shortcut: markers and returns a technical debt ledger, helping developers audit and address deferred code shortcuts.

Instructions

Scan repository for shortcut: markers and return the technical debt ledger.

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

Input Schema

NameRequiredDescriptionDefault
pathNoRepository directory to scan..
markerNoComment marker keyword (default: shortcut).shortcut

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. "Scan" and "return" imply a read-only, non-mutating operation, but the description never states that explicitly, nor does it mention permission needs, behavior on an invalid path, or scan size/performance limits. For a simple read tool this is an acceptable but not rich disclosure.

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?

A single sentence with zero filler, front-loading both the action and the return artifact. Nothing is repeated or padded.

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?

For a two-parameter read tool with no output schema, the description leaves the shape of the "technical debt ledger" unexplained — an agent cannot tell whether it returns a list, a file path, or structured records. It is otherwise sufficient, since the input schema is fully documented.

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 both `path` and `marker` are already fully documented, making 3 the baseline. The description adds only the concrete detail that markers are matched as `shortcut:` comments, which corroborates but does not meaningfully extend the schema.

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?

The description states a specific verb ("Scan") and a concrete resource ("repository for `shortcut:` markers") plus the produced artifact ("technical debt ledger"). An agent can tell this is the debt-scanning tool without opening the schema, though it does not explicitly name how it differs from siblings like pare_check.

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

Usage Guidelines3/5

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

Usage is only implied: the scan-for-markers framing suggests when it fits, but there is no statement of when to prefer it over pare_check, pare_recall, or pare_shrink, and no prerequisites or exclusions. The agent must infer the boundary from the tool name and sibling names alone.

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