Skip to main content
Glama

GTD Brain

by com.gtdbrain
OverviewDiscussionsAdmin

update_card

Use this when the user wants to change what a card says or how it is tagged: retitle it, edit its notes, set or clear its context, link an action to a project or unlink it, or change who it is waiting on and since when. Only the fields passed change; an empty string clears a field. Do not use to put a card in another column or reorder it — use move_card, which takes these same fields. Do not use to finish or remove a card — use archive_card. Returns the updated card.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whoNoNew delegated-to value, e.g. 'Sam'.
notesNoNew notes / body.
sinceNoNew waiting-since value, e.g. '2026-09-01'.
titleNoNew title.
cardIdYesThe card id to edit.
contextNoNew context id, e.g. 'errands', or an empty string to clear it. 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.
projectIdNoProject card id (from list_projects) to put this action under, or an empty string to unlink it. Only actions (Next Actions cards) can belong to a project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "Project card id (from list_projects) to put this action under, or an empty string to unlink it. Only actions (Next Actions cards) can belong to a project.",
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"New context, or an empty string to clear it. 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."New value: +"New context id, e.g. 'errands', or an empty string to clear it. 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."
    • changedInput schema / properties / since / description
      Previous value: -"New waiting-since value."New value: +"New waiting-since value, e.g. '2026-09-01'."
    • changedInput schema / properties / who / description
      Previous value: -"New delegated-to value."New value: +"New delegated-to value, e.g. 'Sam'."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds genuine behavioral context beyond them: patch semantics ('Only the fields passed change'), the empty-string-clears convention, and the return value ('Returns the updated card'). It does not cover auth requirements or what happens to unspecified fields beyond the partial-update note.

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 front-loaded sentences: capability, patch/clear semantics, exclusions, return value. Every sentence carries distinct information with no padding or repetition.

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?

For a 7-parameter partial-update tool with no output schema, the description covers mutation scope, clearing behavior, sibling routing, and the return value. Nothing an agent needs to invoke it correctly 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 description coverage is 100%, so the schema already documents every parameter including the empty-string clearing behavior for context and projectId. The description restates the fields and generalizes the clear convention, adding only marginal value over the structured data. 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?

The description names a specific verb+resource and enumerates exactly what can be changed (title, notes, context, project link, who/since), which maps cleanly onto the schema. It explicitly distinguishes itself from move_card and archive_card by name, so an agent can route 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 (retitle, edit notes, set/clear context, link/unlink project, change delegation), explicit when-not-to-use conditions (column placement, reordering, finishing/removing), and names the correct alternative for each exclusion.

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