Skip to main content
Glama

Add a todo

add_todo

Add a todo to the person's open list. Returns the new todo with its id.

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": {
      "title": "<title>"
    },
    "name": "add_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional notes under the todo, in Markdown.
titleYesOne short line, the way the person would write it on a list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the mutation and safety profile is covered. The description usefully adds the return shape ("the new todo with its id"), which matters because there is no output schema. It does not warn that repeated calls create duplicates (consistent with idempotentHint=false) or say which list the item is added to.

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?

Two short sentences, action stated first and return value second, with no filler. Every sentence earns its place.

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 two-parameter creation tool with full annotation coverage, the definition covers what it does and what it returns. The only real gap is not stating that non-idempotent repeated calls create duplicate todos, which would help an agent avoid accidental duplication.

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 title and body are already documented with guidance (one short line; optional Markdown notes). The description adds no further meaning about formatting, length, or defaults, so the baseline of 3 applies.

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?

"Add a todo to the person's open list" gives a specific verb (add) and resource (todo) plus a scope hint that the new item lands in an open state. It does not explicitly contrast with siblings like edit_todo or complete_todo, so the differentiation is only implicit.

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 list" implies this is for creating new items rather than modifying existing ones, which subtly separates it from edit_todo and complete_todo. However, there is no explicit when-to-use statement, no mention of what to do instead for related operations, and no prerequisites such as required account or list context.

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