Skip to main content
Glama

revise_task

Queues a bounded revision from a changes_requested review so targeted rework is sent to an isolated worker while preserving the original task context.

Instructions

Queue a bounded revision from a changes_requested review.

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": {
      "run_id": "<run_id>",
      "review_id": "<review_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "revise_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
review_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Queue' implies an asynchronous mutation and 'bounded' hints at scope limits, but there is no disclosure of permissions, idempotency behavior, effect on the existing task, or what is returned.

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 front-loaded sentence with no unnecessary wording. It is as concise as possible for the information it contains.

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?

For a mutation tool with no annotations, no output schema, and 0% schema parameter coverage, the description is too thin. It leaves the idempotency contract, required run context, and operational behavior unexplained.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for three undocumented parameters. It only loosely implies the review context and gives no meaning for run_id or idempotency_key.

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 uses a specific verb and object ('Queue a ... revision') and scopes it with a clear source condition ('from a changes_requested review'). It distinguishes the action from a generic task submission, though 'bounded' is left undefined.

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 phrase 'from a changes_requested review' implies the precondition for use, giving useful context. However, it does not state when not to use it or name alternatives such as submit_task or submit_review.

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