Skip to main content
Glama

digest_many

Ask one question across many files and get a short answer with a checked quote per file, enabling surveys of documents or modules without manual reading.

Instructions

Ask the same question of many files (for example every *.md under a folder).

Returns one short answer per file with a checked quote. Use it for surveys such as "which of these documents still mention the old part" or "what does each module export".

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": {
      "root": "<root>",
      "glob": "<glob>",
      "question": "<question>"
    },
    "name": "digest_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
globYes
rootYes
questionYes
max_filesNo
max_words_eachNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the return shape (one short answer plus a checked quote per file), but says nothing about cost or fan-out implications of asking an LLM question per matched file, how partial failures are handled, or what happens when the glob matches nothing or too much.

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?

Three tight sentences: purpose first, return value second, usage examples last. The parenthetical glob example is the only mildly redundant element and it earns its place by making the glob parameter concrete.

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?

An output schema exists, so return values need not be spelled out, and the description still does so adequately. However, for a fan-out tool with five parameters at 0% schema coverage and no annotations, the missing treatment of the two limit parameters and of per-file failure or cost behavior leaves real gaps for an agent deciding how 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 description coverage is 0%, so the description must compensate. It gives natural-language meaning for question ('ask the same question'), glob ('every *.md under a folder') and implicitly root ('under a folder'), but leaves max_files and max_words_each entirely undefined in both schema and description, and does not clarify whether glob is relative to root or absolute.

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 and resource: ask one question across many files matched by a glob, and return one short answer with a quote per file. It distinguishes 'many files' from the single-file sibling implicitly through the plural scope, but never names digest_file or digest_command explicitly, so sibling differentiation is inferable rather than stated.

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?

Two concrete survey examples ('which of these documents still mention the old part', 'what does each module export') make the intended usage pattern clear. There is no guidance on when not to use it, such as routing a single-file question to digest_file or a shell command question to digest_command.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.