Skip to main content
Glama
Sign In
AI Notes MCP Server

AI Notes MCP Server

by ibrahimbelkahla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get note

get_note
Read-only

Retrieve the full content of a personal note by its ID, enabling AI assistants to read stored information for summaries, answers, or quizzes.

Instructions

Read the full content of one note by its id.

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, for example 'a1b2c3d4'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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=true, so the safety profile is covered. The description adds only that the *full* content is returned, which usefully signals no truncation, but says nothing about error behavior for missing notes or content format.

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?

A single front-loaded sentence with zero filler; the verb and scope appear before any qualifier. Nothing could be removed without losing meaning.

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?

For a one-parameter read-only tool with a fully documented schema and a readOnlyHint annotation, the description covers what the agent needs. The only minor gap is not saying what happens when the id does not exist.

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% and the single 'id' parameter includes an example value, so the schema does the heavy lifting. The description adds 'by its id' but no format or validity constraints beyond that.

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?

States a specific verb ('Read') and resource ('one note'), and clarifies it returns the full content of a single note by id. This implicitly separates it from list_notes and search_notes, though it never names those siblings explicitly.

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?

Usage is implied by the phrase 'by its id' — the agent knows to use it when a note id is already known — but there is no explicit statement of when to prefer it over search_notes or list_notes, and no mention of what happens when the id is invalid.

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

Deploy Server

Other Tools