Skip to main content
Glama

Save a durable note

brain_capture

Creates new vault notes in the capture folder with graph-ready frontmatter for plans, decisions, ideas, meeting notes, and session logs, keeping them linked and searchable.

Instructions

Write a new note into the vault's capture folder with graph-ready frontmatter. Use for plans, decisions, ideas, meeting notes, or session logs the owner wants to keep. Not for one-line facts (use brain_remember). The reply lists existing notes the body names without linking.

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": {
      "title": "<title>",
      "body": "<body>"
    },
    "name": "brain_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesMarkdown body. Link related notes inside the sentence that says how they relate, e.g. 'The restore steps are in [[Restore the ledger database]]'; a bare list of links carries little weight.
kindNonote
titleYesSpecific noun phrase, not a filename
topicsNoConcept names, e.g. ['OAuth', 'RAG']
projectNoProject hub name this belongs to, e.g. 'Website Redesign'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.2
    • changedInput schema / properties / body / description
      Previous value: -"Markdown body. Link concepts inline with [[Concept]] on first mention."New value: +"Markdown body. Link related notes inside the sentence that says how they relate, e.g. 'The restore steps are in [[Restore the ledger database]]'; a bare list of links carries little weight."
  2. First observedv0.4.0

TDQS

A4.1/5.0
Behavior3/5

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

The description is consistent with the annotations (write, non-destructive, non-idempotent) and adds useful context: notes land in the capture folder with generated frontmatter, and the reply lists named-but-unlinked notes. With annotations already declaring the safety profile and no output schema, this is helpful but thin — it does not warn about duplicate titles despite idempotentHint=false, nor explain overwrite or failure behavior.

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 tight sentences: what it does, when to use it, when not to. The scoping constraint is front-loaded and no sentence is wasted.

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?

No output schema exists, and the description only partially covers the return value (naming the 'existing notes named without linking' detail). For a 5-parameter write tool that creates files, it lacks any mention of naming collisions, folder resolution, or what happens when the capture folder is missing.

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 80%, so the schema already documents body, title, topics, and project. The description adds no per-parameter guidance beyond the general 'graph-ready frontmatter' framing, and the 'kind' enum is left to the schema's enum and default. Baseline 3 is appropriate.

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 ('Write a new note into the vault's capture folder') plus the distinguishing trait of graph-ready frontmatter. It explicitly separates itself from brain_remember, which is also in the sibling list.

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

Usage Guidelines5/5

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

Names concrete use cases (plans, decisions, ideas, meeting notes, session logs) and an explicit exclusion with the alternative: 'Not for one-line facts (use brain_remember).' Nothing is left to inference.

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