Skip to main content
Glama

Get note

get_note
Read-onlyIdempotent

Retrieve one note or bookmark by ID in full so an AI assistant can attach its complete content as context.

Instructions

Fetch one note or bookmark in full.

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": {
      "note_id": "<note_id>"
    },
    "name": "get_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
uriYesResource URI for this note
urlNoSet for bookmarks
bodyYes
tagsYes
titleYes
created_atYes
updated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and repeatability are covered. The phrase 'in full' adds genuine context beyond the annotations, signaling complete content rather than the truncated results a search would return. Nothing is said about behavior on a missing or invalid ID.

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?

One short sentence with the scope constraint ('one', 'in full') placed where it is immediately useful. Nothing is wasted and nothing is buried.

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?

An output schema exists, so return structure needn't be explained, and the read-only annotations cover the risk profile of a one-parameter lookup. Missing only the not-found behavior and how an agent should source the note_id.

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?

The single note_id parameter has 0% schema description coverage, so the description is the only place meaning could be added. It hints the ID may address either a note or a bookmark, but does not clarify whether the two share an ID space, which is precisely the ambiguity an agent would need resolved.

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?

Specific verb plus resource plus scope: 'Fetch one note or bookmark in full' makes the single-item nature explicit, which separates it from list_notes and search_notes. It stops short of naming an alternative outright, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

The word 'one' implies this is the by-ID retrieval path rather than browsing or searching, but the description never states when to prefer it over search_notes or list_notes, nor any prerequisite for obtaining a note_id. Usage is only implied.

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