Skip to main content
Glama
Sign In
joplin-mcp-server

joplin-mcp-server

by jordanburke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

read_note

Retrieve the full content of a specific note by providing its unique ID, enabling quick access to detailed information stored in the Joplin MCP Server.

Instructions

Read the full content of a specific 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": {
      "note_id": "<note_id>"
    },
    "name": "read_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYesID of the note to read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation, but doesn't mention authentication requirements, rate limits, error conditions, or what 'full content' includes (e.g., metadata, formatting). This leaves significant gaps for a tool that presumably accesses user data.

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?

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a simple read operation and front-loads the essential information.

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?

For a data access tool with no annotations and no output schema, the description is insufficient. It doesn't explain what format the content returns in, whether it includes metadata, or what happens with invalid IDs. Given the context of sibling tools that handle multiple notes and notebooks, more guidance is needed.

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?

The schema description coverage is 100%, with the single parameter 'note_id' clearly documented in the schema. The description adds no additional parameter information beyond what the schema already provides, so the baseline score of 3 is appropriate.

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?

The description clearly states the action ('Read the full content') and resource ('a specific note'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'read_multinote' or 'read_notebook', which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'read_multinote' or 'read_notebook'. It doesn't mention prerequisites, constraints, or typical use cases, leaving the agent to infer usage from context alone.

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

Related Tools