Skip to main content
Glama

GTD Brain

by com.gtdbrain
OverviewDiscussionsAdmin

capture

Use this when the user mentions something they need to do, remember, buy, or follow up on and does not say which list it belongs to: it goes straight to the Inbox in one step, no column lookup (capture first, clarify later). Examples: 'remind me to renew my passport', 'add call the dentist', 'note: look into solar panels'. Do not use when the user names a destination list (Next Actions, Projects, Waiting For, Someday/Maybe, a custom column) or a card kind — use create_card. Do not use to change, move, or finish an existing card, and do not use for something the user says they already did ('Added the invoice', 'called Sam') — that completes an existing card: find it with search_cards and finish it. Returns the created card.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoOptional details the user gave, e.g. 'expires in March, needs two photos'.
titleYesWhat to capture, in the user's words, e.g. 'Renew passport' or 'Call the dentist about the invoice'.
contextNoOptional. Set it only when the user asks for a context, e.g. 'computer'; otherwise leave it out. Never write a context into notes. GTD context id (e.g. calls, computer, errands, home). The user manages their own set — list_contexts shows it, create_context adds one; if unknown, the error lists the valid ids so you can retry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional. Set it only when the user asks for a context, e.g. 'computer'; otherwise leave it out. Never write a context into notes. GTD context id (e.g. calls, computer, errands, home). The user manages their own set — list_contexts shows it, create_context adds one; if unknown, the error lists the valid ids so you can retry.",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / notes / description
      Previous value: -"Optional longer description / body."New value: +"Optional details the user gave, e.g. 'expires in March, needs two photos'."
    • changedInput schema / properties / title / description
      Previous value: -"The card title (the thing to capture)."New value: +"What to capture, in the user's words, e.g. 'Renew passport' or 'Call the dentist about the invoice'."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent), so the description's job is to add beyond that. It does: the 'no column lookup / capture first, clarify later' behavior and the explicit 'Returns the created card' statement tell the agent what happens on success, which annotations do not. It stops short of documenting duplicate handling or failure modes, so not quite a 5.

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?

It is front-loaded with the positive trigger before the negative exclusions, and every sentence carries routing information. It is somewhat long with three example utterances and two prohibition clauses, but nothing is clearly redundant.

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?

No output schema exists, yet the description states the return value, and for a 3-param create tool with full schema coverage the description supplies everything needed: trigger conditions, exclusions, alternative routing, and the success response.

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 the schema already documents title, notes, and context, including the retry-on-error behavior for unknown context ids. The description adds no parameter-level guidance beyond what the schema states, so the baseline 3 applies.

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?

The description states a specific action (capture straight to Inbox in one step) on a specific resource (a card), and explicitly distinguishes itself from create_card and from card-completion flows. An agent can tell it apart from every relevant sibling without opening any schema.

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?

It gives explicit when-to-use triggers with example utterances, names the alternative (create_card) and the exact condition that selects it (user names a destination list or card kind), and rules out mutation/completion cases with pointers to search_cards. This is about as complete as routing guidance gets.

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

All GTD Brain toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources