Skip to main content
Glama

read_note

Retrieve a single note's full body by ID, with optional character truncation, to inspect stored markdown memory content.

Instructions

Read one note's full body by id.

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": {
      "id": "<id>"
    },
    "name": "read_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
maxCharsNoTruncate the body (default 6000, max 20000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it only implies read-only via the word 'Read'. It says 'full body' while the schema defaults to truncating at 6000 characters, and it says nothing about missing-note errors, permissions, or what is actually returned.

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 eight-word sentence with the resource and lookup key front-loaded and no filler. Nothing could be removed without losing content.

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 tool with zero annotations and no output schema, the description should explain return shape and truncation interaction but does not. The tension between 'full body' and the default 6000-character truncation is left unresolved for the agent.

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 coverage is only 50% and the undocumented parameter is the critical required `id`; the description's 'by id' adds no format or provenance detail. Only `maxChars` is explained, and that explanation lives in the schema rather than the description.

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 and resource ('Read one note's full body') plus the lookup key ('by id'), which cleanly separates it from list-style siblings like list_notes. It does not name a sibling or exclusion, so it stops short of a 5.

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-to-use guidance. The phrase 'by id' only weakly implies the agent must already hold an identifier rather than be searching, and nothing tells the agent what to do if it has a title or query instead.

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