Skip to main content
Glama

krusch_fs_read_page

Read-onlyIdempotent

Read a specific page of a file with anchored notes and SHA-256 drift verification to check whether it is valid or stale.

Instructions

Read a specific page of a file along with anchored notes and SHA-256 drift verification (VALID vs STALE_DRIFT).

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_read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
page_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the disclosure that results include anchored notes and a drift verdict with VALID vs STALE_DRIFT states. That is real behavioral context, but it does not explain what STALE_DRIFT means for the caller, how drift is detected, or what happens for out-of-range pages — and with no output schema, the description carries the full return-value burden.

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 no filler; every clause (page scope, anchored notes, drift verification) contributes information about what the call returns.

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?

For a two-parameter tool with no output schema and zero schema description coverage, the definition conveys the core action and return highlights but leaves parameter meaning and the interpretation of drift statuses unaddressed. Adequate to select the tool, thin for invoking it correctly in edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 and largely does not: it never mentions the path argument, the page_number argument, that paging is 1-based, or what page_number=1 means when omitted. 'A specific page' only loosely implies the page parameter.

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+resource: 'Read a specific page of a file', and adds the distinguishing outputs (anchored notes, SHA-256 drift verification). It is clearly not a whole-file read like read_drive_file, but it never names a sibling or says how it relates to krusch_fs_page_tree for discovering pages.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance; paged reading is only inferable from 'a specific page'. An agent gets no cue about how to find valid page numbers (e.g. page_tree) or when a whole-file/blob read would be preferable.

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