Skip to main content
Glama

Get Note

get_note
Read-onlyIdempotent

Fetch one note's full content by its id — use this when you already hold a note id (from an earlier list_notes, a Project association, or a retrieval citation) and need the complete body rather than the truncated preview list_notes returns. Prefer list_notes when you only have a title or topic and need to find the right note first. Returns the note's id, title, full content, source, and agent_access ("collaborate" or "read_only"); read_only notes are still readable here — that setting only blocks writes. Private to the account; read-only.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe note id — from an earlier list_notes, a Project association, or a retrieval citation

Output Schema

NameRequiredDescriptionDefault
idYes
titleYes
sourceYes
contentYes
created_atYes
updated_atYes
agent_accessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/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 useful behavior context beyond that: it returns id, title, full content, source, and agent_access, and clarifies that read_only notes remain readable because that setting only blocks writes. It does repeat the read-only nature of the operation, which is already in annotations, but the added agent_access semantics are valuable.

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?

The description is front-loaded with the core purpose and then adds usage and return context in a structured way. There is some redundancy in restating return fields despite an existing output schema, and the id-source phrasing duplicates the schema, but the wording is otherwise efficient.

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

Completeness5/5

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

For a simple one-parameter read tool with rich annotations, full schema coverage, and an output schema, the description supplies everything an agent needs: when to use it, when to use list_notes instead, what is returned, and the meaning of agent_access. Nothing material is missing.

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 100% for the single required id parameter, and the schema already says where the note id can come from. The description repeats the same sources ('list_notes, a Project association, or a retrieval citation') and does not add further syntax or format guidance beyond the schema, so the baseline of 3 is appropriate.

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 ('Fetch one note's full content by its id') and clearly distinguishes the result from list_notes by contrasting the full body with the truncated preview. An agent can identify the tool's scope without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: use this when you already hold a note id from list_notes, a Project association, or a retrieval citation. It also names the alternative, list_notes, and the condition that selects it when only a title or topic is available.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.