Skip to main content
Glama

read_note

Retrieve the full content of a note from macOS Notes app. Use this tool to access note details stored on your Mac.

Instructions

Read full note content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:33-33 (registration)
    Tool 'read_note' is defined as an entry in the TOOLS array with description 'Read full note content'.
    ["read_note", "Read full note content"],
  • The tool handler is a generic stub that returns an inspection message. It does not implement actual note reading logic — the real server is a native binary.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
    }
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits beyond the read action, such as idempotency, data persistence, or output 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?

Single sentence with no wasted words, front-loaded with the action and resource. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite zero parameters and no output schema, the description fails to mention how the tool identifies which note to read, leaving ambiguity about its context usage.

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?

Input schema has zero parameters, so schema coverage is 100%. The description adds no further meaning, which is acceptable as baseline.

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 clearly states the action (read) and resource (full note content), distinguishing it from sibling tools like list_notes or search_notes.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like list_notes or search_notes, nor any prerequisites or context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server