Skip to main content
Glama

chop_passages

Extracts exact verbatim quotes answering a question from supplied passages and returns passage numbers, character offsets, readable context, plus an ANSWER or SEARCH decision.

Instructions

Cut the exact quotes that answer question out of passages (retrieved snippets, search results, tool outputs). Returns the quotes (verbatim, with passage number and character offsets), a ready-to-read context string, and decision ANSWER (the passages hold the answer) or SEARCH (search again).

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": {
      "question": "<question>",
      "passages": "<passages>"
    },
    "name": "chop_passages"
  }
}

Input Schema

NameRequiredDescriptionDefault
passagesYes
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does well: it explains the return payload (verbatim quotes with passage number and character offsets, a ready-to-read `context` string) and the ANSWER/SEARCH decision semantics. What is missing is failure behavior, e.g. what happens when no passage contains an answer or how the SEARCH branch is meant to be acted on.

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?

Two tight sentences, front-loaded with the action, with the return contract packed into a single parenthetical. Nothing is wasted and no sentence is filler.

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

Completeness4/5

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

For a two-parameter computation tool with no output schema, the description covers inputs and outputs well enough to invoke it correctly. It falls just short on edge cases such as empty or unanswerable passages and does not clarify how the SEARCH decision should drive the next call.

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 0%, so the description must compensate. It defines `passages` semantically as retrieved snippets, search results, or tool outputs, and `question` as the query to answer, which is genuinely useful. It adds no format, size, or array-shape constraints that would let an agent prepare inputs correctly.

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 gives a specific verb and resource: cut exact quotes answering `question` out of `passages`, and names the input domain (retrieved snippets, search results, tool outputs). It is very clear what the tool does, but it never contrasts itself with the sibling `rank_passages`, so the agent must infer when to pick chopping over ranking.

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: the parenthetical listing of snippet/search/tool-output sources tells the agent this is a post-retrieval step, and the ANSWER/SEARCH decision hints at the follow-up loop. There is no explicit when-not-to-use guidance and no named alternative among the siblings.

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