Skip to main content
Glama

Inspect second-brain status

second_brain_status
Read-only

Reports readable Markdown counts and the latest modification time in your vault without changing any files, so you can verify vault size and freshness before searching or reading.

Instructions

Report readable Markdown counts and the latest modification time without changing the vault.

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": "second_brain_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
vaultYes
countsYes
latestModifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 known. The description adds the concrete outputs (counts, latest modification time) but largely restates read-only behavior and does not cover error conditions, what exactly counts as readable, or return format details.

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 a single, front-loaded sentence with no wasted wording. Both requested metrics and the read-only constraint are stated efficiently.

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

Completeness5/5

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

This is a no-parameter inspection tool with an output schema and annotations covering safety and openness. The description states what is reported and confirms no vault mutation, which is complete for the tool's low complexity.

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?

There are zero parameters, so the baseline is 4. The description does not need to compensate for missing parameter documentation, and the empty input schema is consistent with a simple status inspection tool.

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 uses a specific verb (Report) and clearly states the two outputs: readable Markdown counts and latest modification time. It also scopes the operation to the vault. It does not explicitly contrast with siblings such as second_brain_read or second_brain_search, but the inspection/status purpose is distinguishable.

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 'without changing the vault' implies a safe inspection use case, but the description does not state when to use this tool versus alternatives like second_brain_read or second_brain_search. Usage is inferable rather than explicitly guided.

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