Skip to main content
Glama
Sign In
secondbrain-mcp

secondbrain-mcp

by jesusr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Full-text search

search
Read-only

Find pages by names and contents using case- and accent-insensitive matching across all query terms. Returns relevant matches with snippets and optional path filtering.

Instructions

Search page names and contents (case- and accent-insensitive). All terms must match. Returns matching pages ranked by relevance with snippets.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
prefixNoOnly pages under this path, e.g. 'projects' or 'projects/website'
include_systemNoInclude SilverBullet system pages (Library/, Repositories/, SETTINGS, CONFIG)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, and the description adds substantial behavior the annotation cannot: case- and accent-insensitivity, AND semantics across terms, relevance ranking, and snippet returns. It omits details like pagination behavior or the cost of broad queries, keeping it short of 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.

Conciseness5/5

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

Three short sentences, front-loaded with the resource, then matching semantics, then return shape. Every sentence carries distinct information with no filler.

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 what is searched, how matching works, ranking, and return shape, which is enough for a read-only search tool with no output schema. Minor gaps remain around result size limits and the relationship to sibling listing tools.

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%: prefix and include_system are documented in the schema, while query and limit only have type constraints. The description compensates for query by specifying that all terms must match and matching is case/accent-insensitive, which is real added meaning, but says nothing about limit or the default exclusion of system pages beyond what the schema implies.

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 and resource ('Search page names and contents') plus the scope (page names, not tags, tasks, or backlinks). It does not explicitly contrast itself with siblings like list_pages or pages_by_tag, so an agent must infer the distinction from the word 'search'.

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?

No when-to-use guidance and no named alternatives, despite eight sibling tools including list_pages and pages_by_tag that could plausibly overlap. The agent is left to infer that this tool is for term-based queries rather than enumeration.

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