Skip to main content
Glama

Get issue

get_issue
Read-only

Contexto completo de una issue en una sola llamada: identificador legible (TEAM-N), título, descripción markdown, contexto del agente (agentContext), estado, prioridad, asignado, fecha de vencimiento (dueDate, epoch ms), labels, milestone, cycle, sub-issues, comentarios, actividad (issue_events), adjuntos, relaciones (blocks/blocked_by/relates, cada una con el estado de la otra issue; si no puedes verla, solo su identificador y su estado) y los valores de los campos personalizados (customFields). Incluye el estado de trabajo en curso: agentWorking (nombre del agente que la tomó, null si está libre), agentWorkingBy (su userId) y agentWorkingSince. agentCloseState (stateId, name, instruction) es el estado de cierre que el dueño o un admin del workspace ha configurado para el trabajo de los agentes. agentGuidance (workspace, team, instruction) son las instrucciones fijas que una persona del workspace ha escrito para los agentes (convenciones, qué no tocar, cómo cerrar una issue): síguelas; si la del equipo contradice a la del workspace, manda la del equipo. No es memoria tuya (mem_*): la memoria la escribes tú, la guía una persona. Falta si no hay ninguna. agentLifecycle (solo lectura, aditivo) dice qué puede hacer YA el agente con la issue: phase = queued (nada la frena y next_ready_issue la repartirá: agentReady, sin empezar, sin bloqueos, sin lock vigente, no es épica, proyecto activo y escribible), blocked (bloqueadoras sin resolver), ready (nada la bloquea pero NO está en la cola: no marcada agentReady o ya en curso sin dueño; se toma con claim_issue), in_progress_mine, in_progress_other (la tiene otro agente con lock vigente), review (estado started que no es el primero por position) o closed (completed/canceled); blockers (con unblocksOn: estados que las desbloquean); readiness (dorComplete, missing, whyNotInQueue); lock (by, since, expiresAt, expired, mine); transitions[] (a qué estados puede moverla, con kind, isAgentCloseState, claimsLock, clearsAgentFlags, wip y warnings) y nextSteps[].

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": "get_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

A3.8/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint=false, the description discloses lock semantics (by, since, expiresAt, expired, mine), visibility limits on related issues ('si no puedes verla, solo su identificador y su estado'), the full agentLifecycle phase taxonomy, and the precedence rule for agentGuidance. That is substantive context an agent could not get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, but the body is a dense wall of field enumerations in one paragraph with no line breaks or grouping. Given there is no output schema most of the content is defensible, yet it is longer and harder to scan than needed.

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?

With no output schema, the description carries the full burden of explaining the return shape and does so near-exhaustively, including computed fields like agentWorking and agentLifecycle. Minor gaps remain: it does not say whether comments/activity/attachments are truncated or ordered, or how large the payload can get.

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 the single `id` parameter is already fully documented (UUID or TEAM-N, case-insensitive, UUID required on ambiguity). The description adds no format or disambiguation detail beyond that, so the baseline 3 applies.

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?

Opens with a specific verb+resource+scope: 'Contexto completo de una issue en una sola llamada', which tells an agent this is a single-issue detail fetch rather than a list. It also implicitly contrasts with siblings by naming mem_* ('la memoria la escribes tú'), claim_issue and next_ready_issue, but it never explicitly states 'use this instead of list_issues/get_doc'.

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?

Provides behavioral routing inside the payload interpretation ('se toma con claim_issue', 'síguelas; si la del equipo contradice a la del workspace, manda la del equipo'), which is real guidance. However, there is no explicit statement of when to call this tool versus list_issues or another detail source, and no when-not-to-use condition.

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