notes-mcp

Overview Schema Source Related Servers Discussions Admin

get_note

Read-only

Retrieve a single note by its ID or exact title. Returns the full note including body. Use when you know the note's identifier.

Instructions

Retrieve a single note by its ID or exact title.

    Provide note_id OR title (note_id wins if both are given). Returns the
    full note including its body. Use search_notes for fuzzy matching.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_note"
  }
}

Input Schema

Name	Required	Description	Default
`title`	No	Exact title of the note (case-insensitive). Used when note_id is not given; if several notes share the title, the most recently updated one is returned.
`note_id`	No	ID of the note to fetch. Preferred when known.

Output Schema

Name	Required	Description
`id`	Yes	Unique numeric ID of the note.
`body`	Yes	Full body text of the note.
`tags`	Yes	Tags attached to the note.
`title`	Yes	Title of the note.
`created_at`	Yes	Creation time (ISO 8601, UTC).
`updated_at`	Yes	Last modification time (ISO 8601, UTC).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds behavioral details: conflict resolution (note_id wins), case-insensitive title matching, and fallback to most recent if multiple same title. Could mention error handling (e.g., 404 if not found) but output schema might cover that.

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?

Two short sentences plus a bullet. Front-loaded with main action. Every sentence adds value: retrieval method, parameter precedence, fuzzy alternative. No wasted words.

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 get-by-id/title tool, description covers purpose, parameter disambiguation, and when to use sibling tool. Output schema exists, so return format is documented elsewhere. Complete and self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds meaning beyond schema: note_id wins if both given, title is case-insensitive, and if multiple notes share title, most recently updated is returned. These enrich what the schema alone provides.

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?

Description clearly states 'Retrieve a single note by its ID or exact title' with specific verb and resource. Distinguishes from sibling search_notes by mentioning 'fuzzy matching' and from list_recent_notes by indicating single retrieval.

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?

Explicitly provides when to use: 'Provide note_id OR title (note_id wins if both given)'. Also advises alternative: 'Use search_notes for fuzzy matching'. No other sibling tools are appropriate for this exact retrieval.

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

Deploy Server