Skip to main content
Glama

toda_set

Update a deferred issue's status to move it between sections, with optional ref merging and closure notes.

Instructions

Update an item status (moves it between sections)

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>",
      "status": "<status>"
    },
    "name": "toda_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesItem id, e.g. D-017
refNoSpace-separated refs to merge into the item
noteNoClosure note (used when status=x), e.g. the fix commit
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 behavioral burden. It discloses that status changes move an item between sections, but does not explain permission requirements, reversibility, side effects of merging refs, or how closure notes interact with status=x. For a mutation tool with zero annotation coverage, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence with no redundant wording. It is front-loaded with the action and resource. It is arguably too sparse, but that is a completeness issue rather than a conciseness problem.

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

Completeness2/5

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

This is a mutation tool with four parameters, no annotations, and no output schema. The description says very little about state transitions, status codes, side effects, or required context for closure notes. It is not sufficient for an agent to invoke the tool confidently without studying the 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 75%, so most parameters already have schema descriptions. The description adds the conceptual mapping that status changes move items between sections, but it does not explain the enum values o/s/x, when ref or note are needed, or what merging refs does. Baseline 3 is appropriate given moderate-to-high schema coverage and limited added meaning.

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?

The description states a specific verb and resource: 'Update an item status'. The parenthetical adds that this moves the item between sections, which distinguishes it from read-only siblings like toda_list and creation via toda_add. It is clear but does not explicitly name or differentiate alternatives.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as toda_add or toda_prune. The mutation intent is implied by 'Update', but an agent must infer the workflow context.

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