Skip to main content
Glama

Rename a task

rename
DestructiveIdempotent

Updates a task's title to reflect its current content when the existing title is stale or misleading.

Instructions

Retitle a task when the title no longer says what it is. Steps are reword_step, and the page describe or edit_doc.

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>",
      "title": "<title>"
    },
    "name": "rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesThe task id
titleYesThe new title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior2/5

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

The annotations already declare this as a non-readonly, idempotent, destructive mutation, so the safety profile is known without the description. The description adds nothing further: it does not say that the previous title is overwritten and lost, whether permissions are required, or what happens if the task id is unknown.

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?

Two short sentences, front-loaded with the action and its trigger, and no filler. The second sentence is telegraphic to the point of slight ambiguity ('and the page describe or edit_doc'), costing a point but not much space.

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 two-parameter rename tool with full schema coverage and annotations covering the mutation profile, the description supplies the missing piece: which sibling handles steps and pages. Nothing critical is absent, though a note on error behavior for a bad task id would round it out.

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% with only two parameters, both already labeled ('The task id', 'The new title'). The description adds no extra meaning about id format or title constraints, so the schema does all the work and the baseline 3 applies.

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 gives a specific verb (retitle) and resource (task), and then distinguishes this tool from siblings by resource type: steps go to reword_step, pages go to describe or edit_doc. An agent can select this tool without opening any other definition.

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?

It names a clear trigger condition ('when the title no longer says what it is') and routes other resource types to their own tools. The only soft spot is that 'the page describe or edit_doc' leaves it ambiguous which of the two sibling tools a caller should pick for pages.

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