big-brain

by jzhao234

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Capture to inbox

capture

Save a thought, link, or note to an inbox for later processing when it is worth keeping but its destination is unclear.

Instructions

Quick-capture a thought, link, or piece of information into the inbox for later processing. Use when something is worth keeping but you don't yet know where it belongs.

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": {
      "text": "<text>"
    },
    "name": "capture"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	The content to capture (markdown ok)
`title`	No	Optional title; derived from the text if omitted

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 14, 2026

TDQS

A3.8/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 behavioral burden. It discloses the write target (inbox) and the deferred-processing intent, but says nothing about whether titles are deduplicated, whether the capture is reversible, what is returned, or any permission requirements.

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 what happens (capture into inbox) before the usage condition. Every clause earns its place with no redundancy.

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 two-parameter, single-required-field capture tool with no output schema and no annotations, the description covers purpose, destination, and usage condition adequately. Only the return value / post-capture behavior is unaddressed, which is minor here.

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 baseline is 3. The description adds only the general notion of 'a thought, link, or piece of information' and does not elaborate on the two parameters beyond what the schema already documents (including the markdown acceptance and title derivation).

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 (capture) and destination (inbox) plus the kinds of content accepted (thought, link, information). It is clear on its own, but it never names the sibling it most resembles (create_note/append_note), so an agent must infer the distinction from the 'inbox' framing alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when something is worth keeping but you don't yet know where it belongs' is an explicit selection condition, and it implicitly excludes the directed-note siblings. There is no explicit when-not statement or named alternative, which is what keeps it from a 5.

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