Skip to main content
Glama

pare_recall

Recover exact lines or regex matches from a previously shrunk output ID to retrieve original content after compression.

Instructions

Recover exact lines or regex matches from a previously shrunk output ID.

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": {
      "item_id": "<item_id>"
    },
    "name": "pare_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
grepNoRegular expression filter over stored raw lines.
linesNo1-indexed inclusive slice, e.g. `1:50` or `120:160`.
item_idYes12-char SHA-256 content ID printed in the pare footer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/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 only signals that recovery is exact (non-lossy). It says nothing about whether the stored output persists across sessions, what happens with an invalid or stale item_id, whether grep and lines compose, or what the response looks like.

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 front-loaded sentence with no filler; the recovery target and its source are the first things read. Nothing is redundant 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 three-parameter retrieval tool with no output schema and no annotations, the description is minimally viable. It omits failure behavior for unknown IDs and any note on how the two optional filters interact, which an agent would need before relying on 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 description coverage is 100%, so item_id, grep, and lines are already fully documented in the schema, including the slice format and the footer origin of the ID. The description only echoes that lines and regex matches are the two retrieval modes, adding minimal meaning beyond 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 pairs a concrete verb ('Recover') with a concrete resource ('exact lines or regex matches') and names the source ('a previously shrunk output ID'). This makes the read-back counterpart to pare_shrink obvious, though it doesn't explicitly contrast with siblings like pare_check or pare_debt.

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 implied rather than stated: an agent can infer it should call this when it needs the raw content behind a shrunk output. There is no explicit when-not guidance, no mention of what to do if the ID is unknown or expired, and no named alternative.

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