Skip to main content
Glama

pare_shrink

Compress verbose command or file output into a concise summary and return a lossless recall ID so you can retrieve the original later.

Instructions

Compress verbose command/file output and return a lossless recall ID.

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_shrink"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoInput file path (omit to read stdin, or pass raw text via MCP `text`).
textNoInline text payload (primarily for programmatic/MCP calls).
max_linesNoMaximum summary lines for log streams.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It does disclose one important trait beyond the schema: recall is lossless, so original content can be recovered. It does not cover what happens with very large inputs, whether output is stored server-side, permissions, or the format/lifetime of the recall ID.

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?

One short sentence, front-loaded with the action and ending with the key return-value guarantee. Nothing is wasted.

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?

All three parameters are optional and fully documented, and there is no output schema, so the description need not explain a return shape. However, for a tool that returns a retrieval ID, it omits how that ID is consumed and any limits, leaving a real gap for an agent deciding whether to call it.

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 coverage is 100%, with each of file, text, and max_lines documented inline. The description adds no parameter meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Compress verbose command/file output') and adds a return-value fact ('lossless recall ID'). It doesn't explicitly distinguish itself from siblings like pare_recall, but the purpose is unambiguous.

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?

No when-to-use or when-not-to-use guidance. With siblings pare_check, pare_debt, and pare_recall present, an agent gets only an indirect hint via the 'recall ID' mention; nothing says when compression is appropriate versus those alternatives.

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