Skip to main content
Glama

List todos

list_todos
Read-onlyIdempotent

List the person's todos, starred first, then most recently updated. Each row has the id, title, a one-line preview of the body, done, doneAt and important. Open todos by default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_todos"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoopen (default): still to do. done: checked off. all: both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful behavior beyond that: default filtering to open todos, ordering by starred then recently updated, and the specific fields returned per row. It does not mention pagination or result limits, which is a minor gap.

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?

The description is three compact sentences, front-loads the action and ordering, then gives row fields and the default filter. Every sentence adds information without repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with a fully described single filter parameter and annotations covering safety, the description is nearly complete: it covers ordering, row shape, and default filter. It omits any mention of pagination, limits, or whether all todos can be returned at once, which would be useful for a list endpoint.

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%, and the sole filter parameter's enum and meanings are fully documented in the schema. The description only reiterates the default (open) and adds no syntax or semantic detail beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 person's todos") and describes ordering and row contents, so it is clearly a list operation rather than a single-item get. It does not explicitly name or contrast with sibling tools such as get_todo, so it falls short of full sibling differentiation.

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

Usage Guidelines3/5

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

The phrase "Open todos by default" gives useful default context, and the filter enum in the schema covers alternatives. However, there is no explicit when-to-use or when-not-to-use guidance versus get_todo or other siblings, so usage is only implied.

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