Skip to main content
Glama
Sign In
Software Planning Tool

Software Planning Tool

by SolonaBot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

update_todo_status

Update a todo item's completion status to mark it as done or pending, keeping project progress accurate.

Instructions

Update the completion status of a todo item

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>",
      "isComplete": "<isComplete>"
    },
    "name": "update_todo_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
todoIdYesID of the todo item
isCompleteYesNew completion status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a mutating action but doesn't disclose side effects, error handling, permissions, or response behavior. For a write operation, this is a significant gap.

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?

The description is a single, clear sentence that is front-loaded with the specific action. Every word earns its place, with no unnecessary detail or verbosity.

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 simple two-parameter update tool, the description is minimally adequate. However, it lacks usage context and behavioral details that would be helpful given the absence of annotations and output schema, leaving gaps around expected results and side effects.

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?

The input schema has complete descriptions for both parameters (todoId and isComplete), so the description adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate given the 100% schema description coverage.

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 it updates the completion status of a todo item, which is a specific action on a specific resource. This distinguishes it from sibling tools like add_todo/remove_todo and update_goal, which handle different aspects.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention that this should be used for toggling completion status rather than adding/removing todos or updating other goal properties.

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