Skip to main content
Glama

chop_files

Reads local text files, splits them into ~1,000-character passages, and extracts exact quotes answering a question with file path and character offset—avoid reading long files in full.

Instructions

Read local text files (notes, docs, logs, code, exported pages), split them into ~1,000-character passages and cut out the exact quotes that answer question. Each quote carries its file path and character offset in that file. Use it instead of reading long files in full when only part of them is relevant.

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>",
      "paths": "<paths>"
    },
    "name": "chop_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and discloses the core pipeline: reading local text files, splitting into ~1,000-character passages, and returning exact quotes with file paths and character offsets. It reasonably implies read-only behavior through 'Read local text files,' but it does not mention access expectations, file limits, or error behavior.

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?

The description is three focused sentences, front-loads the operation, and every clause adds useful information about scope, processing, output metadata, or usage. There is no unnecessary repetition.

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?

There is no output schema and no annotations, but the description explains the core behavior and return metadata sufficiently for an agent to understand what it will get back. It is slightly incomplete because it does not fully document the `paths` parameter format or the overall response organization.

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 names `question` as the target for extraction and implies `paths` through 'Read local text files' and 'Each quote carries its file path,' but it never explicitly states that `paths` is an array of local file paths or specifies path format, leaving some ambiguity.

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 operation: read local text files, split them into ~1,000-character passages, and extract exact quotes that answer `question`. It is clear what the tool does, but it does not explicitly differentiate itself from the sibling tools `chop_passages` or `rank_passages`.

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

Usage Guidelines4/5

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

It gives a clear usage condition: use it instead of reading long files in full when only part of them is relevant. It does not name alternatives or state when not to use it, so the guidance is strong but not exhaustive.

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