Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

get_note

Read-only

Read a complete note as Markdown with its current version to retrieve truncated search results or check the version before updating.

Instructions

Read one whole note as markdown, with its current version. Needed only for notes search_notes marked truncated, or to get the version before update_note.

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
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

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=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return shape (markdown, whole note, current version attached) and the version-capture workflow that motivates calls. It does not cover edge behavior such as what happens for a missing or trashed note, which keeps it short of a 5.

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 sentences with no filler: the first defines the output, the second defines when to call it. The triggering condition is front-loaded in the second sentence and no wording is redundant.

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?

With no output schema, the description correctly carries the return-format information (markdown plus current version), and it is sufficient for a one-parameter read tool. The remaining gap is that neither the parameter's meaning nor the behavior for invalid or trashed notes is addressed, but that is minor relative to the low complexity.

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%, so the single 'id' property is documented nowhere, and the description never states that the parameter is a note identifier or what format it takes. The phrase 'one whole note' implies the id selects a note, which is minimal compensation for the coverage gap. Adequate but with a clear gap.

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 one whole note as markdown') plus the notable payload detail that the current version is included. It also distinguishes this from search_notes by scoping it to notes that search flagged as truncated, so an agent can separate it from the bulk-search sibling without opening a 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?

The description gives an explicit gating condition ('Needed only for notes search_notes marked truncated') and a second concrete trigger ('to get the version before update_note'), which also implies a sensible alternative for full-note retrieval. The word 'only' actively prevents over-calling, which is exactly what usage guidance should do.

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