Skip to main content
Glama

Capture an explicit second-brain inbox item

second_brain_capture
Idempotent

Captures user-selected text into the local 00_Inbox/WorkBuddy inbox, redacting common credentials and preventing duplicate saves by content.

Instructions

Save text explicitly marked by the user for retention into 00_Inbox/WorkBuddy. The tool redacts common credentials, is idempotent by content, and cannot write the evidence or knowledge layers.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe exact user-selected text to retain.
titleNo
sourceNo
sourceUrlNo

Output Schema

NameRequiredDescriptionDefault
pathYes
createdYes
redactedYes
captureIdYes
gitCommitRequiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover idempotency, non-destructiveness, and closed-world scope, yet the description still adds real value: credential redaction before persistence and a hard boundary on which layers are writable. It does not say what a deduplicated/idempotent hit looks like to the caller, but the output schema presumably carries that.

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 sentences, front-loaded with the action and destination, then the three behavioral guarantees. No filler or restatement of the name.

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?

An output schema exists so return values need no prose, and the safety/scope profile is well covered. The remaining gap is the three undocumented optional parameters, which leaves an agent guessing how to populate source and sourceUrl.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% – just `text` is documented – and the description adds nothing about `title`, `source`, or `sourceUrl`. An agent gets no guidance on whether source should be inferred, what sourceUrl is for, or how title affects storage, so the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Save text ... into 00_Inbox/WorkBuddy') and scopes it to text 'explicitly marked by the user'. The clause about not being able to write the evidence or knowledge layers distinguishes it from sibling write paths such as upsert_card or record_event.

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?

Gives a clear activation condition: only content the user has explicitly marked for retention. It also implicitly excludes other layers via the 'cannot write' clause, but it does not name a sibling alternative or state what to do when content belongs in the knowledge layer instead.

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