Skip to main content
Glama
Sign In
konbu

konbu

by krtw00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

reopen_todo

Reopen a completed todo item by its UUID, transitioning it from 'done' to 'open' status. Undo a completion to make the todo active again.

Instructions

Reopen a completed todo (transition status from "done" back to "open"). Use this when the user wants to undo a completion. Returns the string "reopened" on success. Example: {"id":"def67890"} → "reopened". Side effects: idempotent — calling on an already-open todo is a no-op that still returns success.

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
idYesUUID of the completed todo to reopen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • addedInput schema / properties / id / description
      Added value: +"UUID of the completed todo to reopen."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are provided, so the description fully carries the burden. It discloses idempotence (calling on already-open todo is a no-op but returns success) and the return value 'reopened', offering comprehensive behavioral insights.

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?

Three sentences convey the action, usage, and side effects with an example. No unnecessary words; highly efficient.

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

Completeness5/5

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

For a simple tool with one parameter, the description covers operation, conditions, idempotency, and return value. No gaps given the complexity and available 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% with a good description for the 'id' parameter. The tool description does not add new semantics beyond the schema, but the example with a UUID is helpful. Baseline 3 is appropriate.

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 description clearly states the tool reopens a completed todo by transitioning status from 'done' to 'open'. It distinguishes itself from sibling tools like mark_todo_done and create_todo by specifying the exact action.

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 description explicitly says 'Use this when the user wants to undo a completion', providing clear context. It lacks explicit mention of alternatives but the sibling list includes mark_todo_done, implying the opposite. The example and side effects further clarify usage.

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