Skip to main content
Glama
Sign In
secondbrain-mcp

secondbrain-mcp

by jesusr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List pages

list_pages
Read-only

Browse pages in a SilverBullet space with last-modified dates and sizes, optionally filtering by path prefix or including system pages.

Instructions

List pages in the second brain (SilverBullet space) with last-modified date and size.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the safety profile is covered, and the description adds useful return-shape context (last-modified date and size). However, it says nothing about ordering, default exclusion of system pages, or result size limits, which are the behaviors an agent would most want to know beyond the schema.

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?

A single front-loaded sentence with no filler; the scope and returned fields are stated immediately. It is efficient, though the parenthetical 'SilverBullet space' is slightly redundant with the title.

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 simple read-only listing tool there is no output schema, and the description does partially compensate by naming returned fields. Still missing is any mention of ordering or how results are limited, which matters for an agent deciding between this and recent_pages.

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 description coverage is 100%, so both the 'prefix' path filter and 'include_system' flag are fully documented in the schema. The description adds no parameter meaning on top of that, which is the expected baseline when the schema does the heavy lifting.

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 a specific verb and resource ('List pages in the second brain (SilverBullet space)') and names the fields returned ('last-modified date and size'). It does not differentiate itself from close siblings like recent_pages or search, which also surface page listings, so an agent still has to infer which is appropriate.

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?

There is no when-to-use or when-not-to-use guidance and no alternatives are named. With siblings such as list_tags, recent_pages, and search, an explicit routing hint (e.g. 'use recent_pages for recency-ordered listings') would be needed to earn a higher score.

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