Skip to main content
Glama

Rewrite an open step

reword_step
Destructive

Rewrite the wording of an unticked step in an open task by task ID and current step text; ticked steps are refused, so untick first if needed.

Instructions

Rewrite an unticked step of an open task. A ticked step is refused: untick it first if your tick was a mistake.

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": {
      "task": "<task>",
      "step": "<step>",
      "text": "<text>"
    },
    "name": "reword_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepYesThe step, by its text as `read` shows it
taskYesThe task id
textYesWhat the step says now, at most 100 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the mutation profile is covered. The description adds value beyond that by disclosing an error path — the call is refused for ticked steps — and the recovery action, information the annotations do not carry. It stops short of saying whether the previous step text is recoverable after the rewrite.

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 primary capability front-loaded and the refusal precondition immediately after, with no filler. Every clause carries actionable information.

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

Completeness4/5

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

For a three-parameter mutation tool with full schema coverage and a safety-relevant annotation set, the definition covers purpose, precondition, and recovery path. The only meaningful gap is not stating whether the prior text is lost or versioned, which matters given destructiveHint=true.

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 description coverage is 100% and each of the three required parameters is documented in the schema, including the text-as-shown addressing for `step` and the 100-character limit. The description adds only the implicit framing that the `task` must be open and the `step` unticked, so baseline 3 is appropriate.

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 and resource ("Rewrite an unticked step") plus the scope constraint ("of an open task"), so the agent knows exactly which object is mutated. The resource noun "step" implicitly separates it from note/doc siblings like reword_note, but no sibling is named as an alternative, so it falls short of a 5.

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?

Gives an explicit when-not condition ("A ticked step is refused") and routes the agent to a named alternative ("`untick` it first"), which is exactly the sort of precondition guidance that prevents a failed call. It does not address when to prefer this over the broader edit/reword family, so it is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.