Skip to main content
Glama

Reopen a todo

reopen_todo
Idempotent

Uncheck a done todo so it is back on the open list. Works without a subscription.

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": "reopen_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe todo's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the mutating-but-safe profile is covered. The description adds the state outcome (returned to the open list) and a genuine availability constraint (no subscription needed), but says nothing about what happens if the todo is already open or about the response.

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 with the action and its outcome front-loaded, followed by the availability note. No redundant or filler wording.

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

Completeness3/5

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

For a single-parameter, non-destructive, idempotent mutation with full annotation coverage, the description covers purpose and one real constraint. It leaves edge behavior (reopening an already-open todo, unknown id) and the return value unaddressed, which is a modest but real gap in a short definition.

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?

There is only one parameter and schema description coverage is 100%, so the schema fully documents the id. The description adds no meaning about id format, lookup failure, or accepted identifier sources, so baseline 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?

States a specific verb plus resource ("Uncheck a done todo") and names the resulting state ("back on the open list"). An agent can tell this is the inverse of the complete operation without opening the schema, though no sibling is named explicitly.

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 "a done todo" implies the precondition (only completed todos need reopening), and "Works without a subscription" signals an availability condition. There is no explicit when-not guidance or named alternative such as complete_todo.

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