Skip to main content
Glama

GTD Brain

by com.gtdbrain
OverviewDiscussionsAdmin

list_cards

Read-onlyIdempotent

Use this when you need cards as plain data to reason over — every card in one column, all cards of one kind, all actions in one context, or a project's actions. Filters combine; archived cards only with includeArchived. For the three main lists prefer list_next_actions, list_projects, and list_waiting_for. Do not use to find a card by words in its title — use search_cards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoOnly cards of this kind: 'action' (Next Actions), 'project' (Projects), or 'card' (everything else).
contextNoOnly action cards tagged with this context id, e.g. 'calls'. 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.
columnIdNoOnly cards in this column id (from list_columns).
projectIdNoOnly the actions that belong to this project card id (from list_projects).
includeArchivedNoInclude archived cards. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "Only the actions that belong to this project card id (from list_projects).",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Only action cards with this context. 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: +"Only action cards tagged with this context id, e.g. 'calls'. 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 / kind / description
      Previous value: -"Only cards of this kind."New value: +"Only cards of this kind: 'action' (Next Actions), 'project' (Projects), or 'card' (everything else)."
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond them: filters combine (AND semantics) and archived cards appear only when includeArchived is set. It omits return ordering/pagination, which keeps it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the primary use case, then the filter-combination rule, then the routing/exclusion guidance. No filler and nothing repeated from the schema.

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 read-only, five-optional-param list tool with no output schema, the description covers scope, filter interaction, archival behavior, and sibling routing. An agent has everything needed to invoke it correctly; return-format detail is not required for a plain-data list.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by stating that filters combine and that includeArchived is the gate for archived cards — a cross-parameter interaction the schema does not express. It adds real meaning rather than restating field docs.

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?

Opens with a specific verb+resource+intent ('cards as plain data to reason over') and enumerates the actual result shapes (one column, one kind, one context, a project's actions). It explicitly names the siblings it is not (list_next_actions, list_projects, list_waiting_for, search_cards), so an agent can disambiguate 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?

Gives positive selection criteria ('when you need cards as plain data'), routing rules for the three main lists, and an explicit negative ('Do not use to find a card by words in its title — use search_cards'). This is a full when/when-not/alternative triad.

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