Skip to main content
Glama

mcp_diet_read_spill

Read-onlyIdempotent

Read a bounded slice from an oversized spill file by 1-based line range, UTF-8 byte offset, or RFC 6901 JSON Pointer to inspect large outputs safely.

Instructions

Safely read a bounded slice from an oversized mcp-diet spill file by 1-based line range, UTF-8 byte offset, or RFC 6901 JSON Pointer.

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": {
      "path": "<path>"
    },
    "name": "mcp_diet_read_spill"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the mcp-tool-output-*.json spill file inside the configured spill directory.
endLineNo1-based inclusive end line number to read.
maxBytesNoMaximum UTF-8 bytes to return (capped by the active mcp-diet limit).
startLineNo1-based inclusive start line number to read.
jsonPointerNoRFC 6901 JSON Pointer (e.g. /results/0/title) to extract a nested value from JSON spills.
offsetBytesNo0-based UTF-8 byte offset to begin reading from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive, and closed-world behavior. The description adds that reads are bounded and safe, but it does not explain truncation behavior, return format, or error handling beyond what annotations and schema already cover.

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 a single dense sentence with the purpose and supported modes front-loaded. There is no redundant or filler wording.

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?

Given six parameters and no output schema, the description could do more to clarify return shape and what happens when bounds or maxBytes are exceeded. It is adequate with strong schema and annotation support, but leaves meaningful behavioral questions open.

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%, so each parameter is already described in the input schema. The description usefully identifies the three addressing modes, but it does not explain mutual exclusivity, precedence, or how modes combine.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: read a bounded slice from an oversized mcp-diet spill file. It also names the three supported slicing modes, making the tool distinguishable from unrelated siblings such as analyze, redact, and status.

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 clearly implies usage for reading large spill files in bounded chunks rather than loading the whole file. However, it does not state when to prefer one addressing mode over another or any exclusions.

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