Skip to main content
Glama

get_note

Read-only

Retrieve a note's name, folder, account, dates, plain text body, and attachment list by ID; locked notes are skipped and attachment content needs a separate call.

Instructions

Get one note: name, folder, account, dates and the plain text body (cut at 100000 characters). Locked notes are not read. Attachments are listed (number, name, type) but their content is not returned. Use get_note_attachment for that.

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
idYesNote id from search_notes (it starts with x-coredata://).
include_htmlNotrue to add the HTML body. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral limits: locked notes are skipped, plain text is truncated at 100000 characters, and attachments are listed but their content is not 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?

Four short sentences, front-loaded with the core retrieval behavior. Each sentence adds useful information: returned fields, truncation, locked-note exclusion, attachment listing, and the sibling alternative.

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?

No output schema exists, so the description carries the return-value burden and does so by listing the main fields, truncation behavior, and attachment metadata limits. Combined with the input schema and annotations, it gives the agent enough information to call the tool correctly.

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%, so both parameters are already documented, including id format and include_html behavior. The description adds context about returned body truncation but does not add meaning beyond the schema for the parameters themselves.

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?

States a specific verb and resource: get one note. It also lists the returned fields, so the agent knows exactly what data this tool retrieves and can distinguish it from sibling tools such as get_note_attachment.

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?

Explicitly routes attachment content to get_note_attachment and warns that locked notes are not read. It gives clear context for use, though it does not explicitly state when to prefer this over search_notes beyond the required id coming from search_notes in the schema.

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