Skip to main content
Glama

krusch_fs_page_tree

Read-onlyIdempotent

Inspect a file's structural table of contents (page numbers, section titles, line ranges, SHA-256 hashes) before reading it to target relevant sections and avoid full scans.

Instructions

Inspect the structural table of contents (page numbers, section titles, line ranges, SHA-256 hashes) before reading a file.

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": "krusch_fs_page_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description then adds the valuable piece annotations cannot: exactly what the returned structure contains (page numbers, section titles, line ranges, SHA-256 hashes), which matters because there is no output schema. It stops short of stating size/cost or truncation behavior for large files.

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 the action first and the payoff contents in parentheses. No filler, no restatement of the tool name.

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 one-parameter read-only inspection tool with no output schema, describing the return contents and the pre-read sequencing is the essential information, and both are present. The remaining gap is the unresolved path convention, which the schema does not cover either.

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 0%, so the bare 'path' string is documented nowhere else. The description only indirectly implies path means the file whose structural tree is being inspected; it says nothing about path format, whether it is absolute or relative, or what root it resolves against.

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?

States a specific verb (Inspect) and a concrete resource (the structural table of contents of a file), and enumerates what that tree contains: page numbers, section titles, line ranges, SHA-256 hashes. It partially separates itself from the read sibling by framing this as a pre-read inspection step, but never names the alternative tool explicitly.

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?

The phrase 'before reading a file' gives an explicit ordering cue: call this first, then read the content. What's missing is an exclusion or a named alternative (e.g. 'use krusch_fs_read_page to fetch content'), so the agent must infer which sibling follows.

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