Skip to main content
Glama

list_todos

Read-onlyIdempotent

Retrieve todos filtered by user or completion status, returning open and completed counts so you can see totals without reading the capped full list.

Instructions

List todos with open/completed counts.

    - user_id: only this user's todos (get it from list_users); omit for everyone.
    - completed: true = only completed, false = only open; omit for both.
    Prefer these filters over reading the whole list: rows are capped at 50, the counts are not.
    

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
user_idNonumeric user id from list_users
completedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent read, so the description's job is to add context beyond that, which it does. It discloses the 50-row cap and the important asymmetry that counts are not capped, which changes how an agent should interpret partial results. It does not describe ordering or anything about the count object's shape, keeping it just 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?

The summary sentence is front-loaded, and each bullet covers exactly one parameter with no repetition of the schema. The closing note on row caps earns its place by justifying the filter-first advice.

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?

With no output schema, the description is responsible for explaining returns, and it does so by naming rows plus open/completed counts and the 50-row cap. The remaining gap is that it never says what an agent should do once the cap is hit, since no pagination parameter exists, leaving the truncated-result path unclear.

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

Parameters5/5

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

Schema coverage is only 50% (completed has no schema description), so the description must compensate, and it does: it defines the true/false/omit tri-state for completed and the everyone-vs-single-user semantics for user_id. It also points to list_users as the source of a valid numeric user_id, going beyond the schema's own hint.

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 first line gives a specific verb and resource ("List todos") and states the return content (open/completed counts), which no sibling tool provides. It also names the sibling (list_users) that supplies the user_id input, so an agent can tell the tools apart immediately.

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

Usage Guidelines4/5

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

The bullets give explicit when-to-use conditions: include user_id for a single user, omit for everyone; set completed true/false for a subset, omit for both. It further directs the agent to prefer these filters over reading the whole list because rows are capped at 50. There is no stated exclusion against any alternative tool, but the guidance is otherwise concrete.

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

Deploy Server

Other Tools