Skip to main content
Glama

Read a note

read_note
Read-onlyIdempotent

Retrieves a complete note from Thread memory by path from search or list results, enabling assistants to recall saved Markdown notes and chat logs.

Instructions

Read a full note from Thread memory, using a path from search_memory or list_memory.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that it returns the 'full' note and that paths originate from the memory search/list tools, but it says nothing about missing-path errors or note-not-found behavior. That is modest added value on top of rich annotations and an output schema.

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 sentence with zero filler, front-loading the action and resource before the path-provenance detail. Every clause earns its place.

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 tool with rich annotations and an output schema, the description covers purpose, scope, and where the argument comes from. The only meaningful omission is failure behavior for invalid paths, which is minor given the structured fields already supplied.

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 description coverage is 0% and the schema only names the field 'path' with type string, so the description must carry parameter meaning. It does identify the provenance of valid values (paths from search_memory or list_memory), but it does not describe the path format or what an acceptable value looks like. Partial compensation, hence a 3.

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 full note from Thread memory') and distinguishes itself from the retrieval siblings by framing search_memory and list_memory as the sources of its path argument. An agent can tell what this tool returns (a full note) versus what the list/search tools return without opening any schema.

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 gives a clear usage context and prerequisite: call this after obtaining a path from search_memory or list_memory, which implicitly routes the agent to those tools first. It stops short of stating exclusions or failure behavior (e.g., what to do if the path is stale or invalid), so it is strong but not fully specified.

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