Skip to main content
Glama

Read second-brain note

second_brain_read
Read-only

Read a Markdown note returned by search to inspect its full content by vault-relative path, with a character limit to control output size.

Instructions

Read a Markdown note returned by second_brain_search. Hidden tool/config paths are blocked; 01_Sources is readable but never writable.

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

Input Schema

NameRequiredDescriptionDefault
pathYesVault-relative Markdown path.
maxCharsNo

Output Schema

NameRequiredDescriptionDefault
pathYes
contentYes
truncatedYes

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 and openWorldHint=false, so the safety profile is covered. The description adds real access-policy context (hidden tool/config paths blocked, 01_Sources readable but never writable), but 'never writable' largely restates readOnlyHint and nothing is said about what happens on a blocked path or how maxChars affects the result.

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?

Two short sentences, front-loaded with the action and the source of the path, followed by the access constraint. No filler or redundant restatement of the title.

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 simple two-parameter read tool with annotations covering safety and an output schema covering the return shape, the description supplies the key scoping and access rules. The only notable gap is any indication of how maxChars truncates or limits returned content.

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 coverage is 50%: 'path' is documented in the schema, while 'maxChars' has only numeric bounds and no explanation anywhere. The description does add semantic meaning about which paths are valid (blocked tool/config paths, 01_Sources readable), which is genuine value beyond the schema, but it leaves maxChars/truncation entirely unaddressed.

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 ('a Markdown note') and anchors it to the sibling that produces the path (second_brain_search), so an agent can tell it apart from capture/recall/core_context tools. It stops short of a full 5 because it doesn't explicitly contrast with other read-ish siblings.

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 'returned by second_brain_search' implies the intended workflow (search first, then read by path), which is useful routing context. However, there is no explicit when-not guidance or statement about what to do if the path wasn't obtained from search, and no mention of alternatives.

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