Skip to main content
Glama

krusch_fs_remember_on_page

Pin durable operational notes or warnings to an exact file page, anchored by SHA-256 hash, so agents retain context across sessions.

Instructions

Pin a durable operational note or warning to an exact file page anchored by SHA-256 hash.

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>",
      "note": "<note>"
    },
    "name": "krusch_fs_remember_on_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
pathYes
categoryNoannotation
page_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already disclose the write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description adds that the note is durable and anchored to a content hash, which hints at version-tied persistence, but it never says what happens on hash mismatch, whether re-pinning duplicates, or whether notes survive file edits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the key qualifier ('durable') appears early. It is efficient, though the SHA-256 phrase adds jargon without clarifying the mechanics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with no output schema and 0% schema coverage, the description is too thin. It leaves the hash anchoring behavior, category semantics, page numbering, and post-write effects entirely unexplained.

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 carries the full burden, yet it only loosely maps to 'path' and 'note'. It says nothing about the 'category' enum (annotation/warning/summary/todo), the default of 'annotation', or what 'page_number' means (1-based page within a file).

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 ('Pin') and resource ('durable operational note or warning') applied to 'an exact file page', which is concrete enough to distinguish it from reads like krusch_fs_read_page or context memory tools. The 'anchored by SHA-256 hash' detail is unexplained and muddies the picture slightly, and no sibling is named explicitly.

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?

No when-to-use guidance beyond the adjective 'durable', and no exclusions or alternatives. An agent cannot tell from this text whether to use it instead of krusch_context_remember for a persistent note, or when the file-page anchor is preferable.

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