Skip to main content
Glama
markdown-memory-mcp

markdown-memory-mcp

by amercans

read_note

Retrieve the full content of a single Markdown note by file name or frontmatter name, including its path and description.

Instructions

Read one note in full.

Args: name: The note's file name without .md, or its frontmatter name. Paths are refused.

Returns {name, path, description, content}, where content is the whole file.

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": {
      "name": "<name>"
    },
    "name": "read_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does meaningful work: it states that paths are refused (a non-obvious input restriction) and enumerates the returned fields with the note that content is the whole file. It omits edge behaviors such as what happens when no note matches or when names collide, which is why it is not 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loaded, with the core action in the first sentence and the constraint and return shape following immediately. The 'Args:' block is a docstring artifact but is compact enough to earn its place by carrying the parameter semantics.

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 single-parameter read tool with no output schema, the description covers the input format, the input restriction, and the return shape, which is close to everything an agent needs to call it. Missing only failure modes and duplicate-name resolution, which are minor for this complexity level.

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 coverage is 0% and the only schema text is a bare 'Name' string, so the description must compensate and largely does: it specifies the file name form without the .md extension, the alternative frontmatter name form, and that paths are rejected. The only gap is the unresolved case of duplicate names across the vault.

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 opens with a specific verb and resource, 'Read one note in full,' which clearly distinguishes this from a broad search or listing operation. It does not explicitly name the sibling tools, but 'one note in full' is concrete enough that an agent can tell it apart from search_notes 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 Guidelines3/5

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

The phrase 'in full' implies this is the tool to use when the complete note body is needed rather than a search result snippet, and the refusal of paths hints at a name-based lookup workflow. However, there is no explicit statement of when not to use it or which sibling to choose instead, so the routing guidance is only implied.

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