Skip to main content
Glama
Sign In
Software Planning Tool

Software Planning Tool

by SolonaBot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

remove_todo

Remove an existing todo item from the current plan by providing its ID. Keep your project plan organized and up to date.

Instructions

Remove a todo item from the current plan

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": {
      "todoId": "<todoId>"
    },
    "name": "remove_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
todoIdYesID of the todo item to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. The verb 'Remove' clearly signals a mutating operation, and no contradictory behavior is stated. However, it does not disclose whether the removal is permanent, any required prerequisites, or side effects on the plan.

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, direct sentence with no redundancy. It is appropriately sized and front-loaded with the action.

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 one-parameter mutation with no output schema or annotations, the description clearly states the action and scope. However, it omits details about return values, error conditions, or prerequisites, and the meaning of 'current plan' is left implicit. These gaps limit its completeness.

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

Parameters4/5

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

The schema fully documents todoId, and the description adds the important context that removal occurs 'from the current plan', which hints that todoId must belong to an active plan. This contextualizes the parameter beyond its basic ID label.

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 uses the specific verb 'Remove' with resource 'a todo item' and scope 'from the current plan', clearly distinguishing it from sibling tools like add_todo, get_todos, and update_todo_status.

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 description implies a use case (removing an item) but provides no explicit guidance on when to use this tool over alternatives such as update_todo_status (which changes status) or explicit exclusions. Sibling tools exist but are not referenced.

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