Skip to main content
Glama

Change issue state

change_issue_state
Idempotent

Mueve una issue al workflow state stateId (sale de list_workflow_states). Fija ese estado tal cual, sin promoverla a otro, y setea started_at/completed_at/canceled_at según su type. Pasarla a un estado de type started la reclama para ti (el mismo lock que claim_issue); release_issue la suelta. Cerrarla (completed/canceled) suelta el lock sola. Si OTRO agente tiene un lock vigente sobre la issue, el cambio se aplica igualmente (no se rechaza) y la respuesta trae warnings con quién la tiene y hasta cuándo.

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>",
      "stateId": "<stateId>"
    },
    "name": "change_issue_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAdmite el UUID de la issue o su identificador legible (TEAM-123, el que se ve en la app), sin distinguir mayúsculas. Si ese identificador existiera en varios de tus workspaces hay que pasar el UUID.
stateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With annotations covering safety (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description still adds substantial behavior: started_at/completed_at/canceled_at are set based on the state type, closing the issue releases the lock automatically, and conflicting locks produce `warnings` with holder and expiry. What it doesn't cover is the failure surface (issue not found, invalid stateId, cross-team state)

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?

Front-loaded with the core action and effect, then the lock semantics and the warning behavior. Every sentence adds information, though the dense run-on style and the parenthetical asides make it slightly harder to scan than a list-like structure would.

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?

No output schema exists, and the description still documents the salient response element (`warnings` with lock holder and expiry) as well as the timestamp side effects. For a 2-parameter mutation this is close to complete; only error conditions and stateId validation rules are absent.

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

Parameters4/5

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

Schema coverage is only 50% – `id` is well documented in the schema, but `stateId` has no schema description. The description compensates by explaining that stateId is a workflow state sourced from list_workflow_states and that its `type` drives the timestamp side effects, which is meaning the schema does not provide.

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?

States a specific verb and resource ('Mueve una issue al workflow state stateId') and immediately names where stateId comes from (list_workflow_states), which distinguishes it from siblings like claim_issue or save_issue. The scope ('Fija ese estado tal cual, sin promoverla a otro') is precise enough that an agent knows exactly what will change.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the conditions under which it should be used versus adjacent tools: it says moving to a started state claims the issue the same way claim_issue does, and that release_issue is the way to drop the lock. It also covers the concurrent-lock case and warns the change is applied anyway, so the agent knows what to expect instead of choosing another tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources