Skip to main content
Glama
inkdropapp

Inkdrop MCP Server

Official
by inkdropapp

read-note

Retrieve the full contents of a note by ID, with optional embedded template instructions for fill-out guidance.

Instructions

Retrieve the complete contents of the note by its ID from the database. A note created from a template has a sourceTemplateId; when present, the response includes a resource link to that source template, whose body holds the fill-out instructions and examples. Read the template (or pass includeTemplate: true) before completing the note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteIdYesID of the note to retrieve. It can be found as `_id` in the note docs. It always starts with `note:`.
includeTemplateNoWhen true and the note has a `sourceTemplateId`, also fetch that template and embed its body (the fill-out instructions and examples) as an extra text block, so you get the note and its template in one call.
Behavior4/5

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

Discloses response behavior for template notes (resource link), content of template, and optimization via includeTemplate. With no annotations, description carries full burden and does well.

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?

Three sentences, front-loaded with main action, each sentence adds unique information. No superfluous text.

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?

Covers main retrieval use case and the template special case. Without output schema, explains response structure adequately. Could mention return type more explicitly.

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

Parameters4/5

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

Schema covers both parameters explicitly. Description adds value by noting noteId format and elaborating that includeTemplate embeds template body as extra text block.

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?

Clearly states action: retrieve complete contents by ID. Distinguishes from siblings by specifying it reads a single note, but does not explicitly contrast with 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 Guidelines3/5

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

Provides workflow advice (read template before completing note) and explains when to use includeTemplate. Lacks explicit exclusions or comparisons to sibling tools.

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/inkdropapp/mcp-server'

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