Skip to main content
Glama

Release issue

release_issue
Idempotent

Libera una issue que tenías en curso (limpia agentWorkingBy/agentWorkingSince), para que deje de aparecer como 'en curso' en la UI y para otros agentes. Solo quien la tomó —o un admin del workspace— puede liberarla (el error nombra a quien la tiene). No cambia el estado: una issue en In Progress sigue ahí y NO vuelve a la cola de next_ready_issue, que solo reparte issues sin empezar; para devolverla a la cola, muévela a un estado sin empezar con change_issue_state y marca agentReady con save_issue. Cerrarla (completed/canceled) ya suelta el lock sola.

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (non-destructive, idempotent), the description discloses the permission model, the fact that the error names the current holder, that no state transition occurs, and that the issue does not re-enter the next_ready_issue queue. These are behavioral consequences an agent could not infer from schema or annotations.

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?

The core action and its effect are front-loaded in the first clause, and every subsequent clause (permissions, no state change, no requeue, alternatives, close-releases-lock) contributes distinct, non-redundant information.

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

Completeness5/5

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

For a single-parameter, non-destructive, idempotent tool with no output schema, the description covers the permission constraint, the exact side effect, the side effects that do not occur, and the correct alternatives. Nothing needed to call or interpret it correctly is missing.

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 100% and the only parameter's schema description already explains UUID vs. human-readable identifier and the multi-workspace disambiguation. The prose adds nothing about the id parameter, so the baseline of 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?

'Libera una issue que tenías en curso' names a specific verb and resource, and immediately states exactly what the operation clears (agentWorkingBy/agentWorkingSince). It also distinguishes the tool from claim_issue and change_issue_state by noting the state is not modified.

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?

Explicitly covers when to use (you hold an in-progress issue and want to stop appearing as 'en curso'), who may use it (taker or workspace admin), and what it is NOT for, routing the agent to change_issue_state plus save_issue with agentReady to requeue. It even notes that closing the issue releases the lock automatically, giving a complete decision map.

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