Skip to main content
Glama

List Todos

list-todos
Read-only

List the team's to-do list for this property: follow-ups the team or the AI noted down to act on later. Check the open items at the start of an analysis, before the first write on a property (save_todo, create_annotation, save_memory; use no search filter for that check), whenever list_properties or a to-do reminder in a tool result shows a due item, and when the user asks what to work on. Tick off anything the conversation shows is done (with save_todo). The needs_attention list holds every overdue or soon-due open item whatever filter you pass: tell the user about each one you have not mentioned yet in this conversation, even when it is unrelated to the current task. Ids look like "t:1a2b3c4d" and are for tool calls only: users never see them, so always name a to-do by its title in replies and in notes.

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": {
      "property": "<property>"
    },
    "name": "list-todos"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoOptional text to match in titles and notes
statusNoWhich to-dos to return (default: open)
propertyYesID of the AIdata property this call targets. Call the list_properties tool to see the properties you can access.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that the needs_attention list returns every overdue or soon-due open item regardless of filter and requires telling the user about each unmentioned one. It also reveals the ID format ('t:1a2b3c4d'), that IDs are for tool calls only, and that users must be given titles instead. These are non-obvious behavioral details that materially affect correct use.

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?

The description is front-loaded with the purpose and then proceeds through triggers and behavioral caveats in a logical order. Most sentences carry actionable information, but the parenthetical about save_todo, create_annotation, and save_memory is slightly dense. It is longer than typical, though justified by the amount of non-obvious behavior it conveys.

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?

There is no output schema, but the description explains the important return shape: the needs_attention list and the ID format. It also covers the key workflow constraints around mentioning overdue items and naming to-dos by title. For a read-only listing tool with annotations already covering safety, this is complete.

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?

The schema already covers all three parameters at 100% coverage, so the baseline is 3. The description adds useful guidance beyond the schema by specifying that no search filter should be used for the pre-write check, implying when to leave search empty. It otherwise defers to the schema for status and property details.

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 verb and resource: 'List the team's to-do list for this property' and defines those items as follow-ups noted by the team or AI. It distinguishes the tool from siblings by naming save_todo, create_annotation, save_memory, and list_properties in related workflows. An agent can immediately tell this is a read-only listing tool for property-scoped to-dos.

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 triggers: 'at the start of an analysis', 'before the first write on a property', 'whenever list_properties or a to-do reminder shows a due item', and 'when the user asks what to work on'. It also names the alternative action for ticking items off ('with save_todo') and specifies using no search filter for the pre-write check. The when-to-use guidance is unusually complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources