Skip to main content
Glama

doer_delete_todo_list

Permanently deletes a todo list and its context attachments from Doer by ID, removing the list and related files when they are no longer needed.

Instructions

Permanently delete a todo list and its context attachments from Doer

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": {
      "id": "<id>"
    },
    "name": "doer_delete_todo_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the todo list to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two important traits: deletion is permanent and it cascades to context attachments. It omits other behavioral facts an agent needs, such as required permissions, whether confirmation is expected, and what happens when the id does not exist.

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?

A single sentence with zero filler; the destructive nature and the cascading side effect are front-loaded where an agent will read them.

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 one-parameter destructive call, the essentials are covered: what is removed, that it is permanent, and that attachments go with it. The remaining gap is post-call behavior on success or invalid id, which matters somewhat given there is no output schema.

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 coverage is 100% and there is only one required integer id, so the schema already documents the parameter fully. The description adds no format or constraint detail beyond it, which is acceptable but makes it a baseline case.

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?

States a specific verb and resource ('delete a todo list') plus a non-obvious scope detail ('its context attachments'), which separates it cleanly from doer_update_todo_list and doer_get_todo_list. It stops short of naming an alternative explicitly, so it is clear but not sibling-differentiating in the strongest sense.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance; the only implied signal is 'Permanently', which hints caution but does not tell an agent when to prefer this over removing items or attachments individually. Alternatives the agent would need to weigh (doer_delete_attachment, updating a list to empty) are not referenced.

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