Skip to main content
Glama
Sign In
SecondBrain MCP

SecondBrain MCP

by vladilenm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

read_notes_batch

Read multiple notes simultaneously to build context, with missing paths reported separately.

Instructions

Read multiple notes in one call for context building. Returns missing paths separately.

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

Input Schema

NameRequiredDescriptionDefault
pathsYesNote paths, names, or aliases
include_contentNoInclude markdown body (default true)
max_chars_per_noteNoOptional content truncation per note
include_frontmatterNoInclude parsed frontmatter (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds the behavioral detail 'Returns missing paths separately,' which is useful. However, it does not disclose other traits like read-only nature, authentication needs, or rate limits, which would enhance transparency.

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 extremely concise, consisting of two sentences with no extraneous information. It front-loads the purpose and includes a key behavioral promise (missing paths). Every word earns its place.

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

Completeness3/5

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

For a tool with four parameters, no output schema, and no annotations, the description adequately states the core functionality but lacks details on the response structure (e.g., format of returned notes and missing paths). This leaves the agent partially uninformed about the output.

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?

With 100% schema description coverage, the baseline is 3. The description does not add additional semantic meaning beyond what the schema already provides for the four parameters. The usage hint 'for context building' is contextual, not parameter-specific.

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 states 'Read multiple notes in one call for context building,' which clearly indicates the tool's purpose as a batch read operation for gathering context. It distinguishes from single-note tools like get_note, but does not explicitly differentiate from 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 description implies usage when multiple notes are needed for context building, but lacks explicit guidance on when not to use this tool versus alternatives (e.g., get_note for single note, list_notes for listing). No exclusions or prerequisites are mentioned.

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