Skip to main content
Glama

get_task_detail

Read-onlyIdempotent

Una tarea entera, por su id: todos los campos, sin recortar la descripción.

Usar cuando hace falta el contexto completo de UNA tarea — la descripción
larga (get_tasks la trae igual pero la lista es más ruidosa), de qué recap
salió, quién es el responsable, qué tramo tiene, si está en el backlog.

Devuelve además `comentarios`: cuántos tiene y el último. El hilo entero
se lee con get_task_comments.

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_id": "<task_id>"
    },
    "name": "get_task_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesID numérico de la tarea (campo 'id' de get_tasks)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real value beyond them: it clarifies that no field is truncated and that a `comentarios` summary (count plus last comment) is returned, preempting the assumption that it returns the full thread. It says nothing about size limits or pagination, which keeps it below a 5.

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?

Three short blocks in a sensible order: what it returns, when to use it, and what it returns in addition. The parenthetical about get_tasks earns its place as routing information, but the phrasing is slightly conversational rather than maximally tight.

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 burden of explaining returns, and it does so partially: untruncated fields, recap origin, assignee, tramo, backlog state, plus the comment summary. That is enough to call it correctly for a two-parameter read tool, though the field list is illustrative rather than exhaustive.

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 both parameters — including the subtle workspace_id fallback of "todos los workspaces" — are documented in the schema itself. The description only says "por su id" and adds no syntax or format detail beyond that, so the schema does the heavy lifting 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?

States a specific verb and resource ("Una tarea entera, por su id: todos los campos, sin recortar la descripción") and pins the scope to a single task. It explicitly separates itself from get_tasks (same data, noisier list) and get_task_comments (full thread), so an agent can choose without opening a schema.

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?

Gives an explicit trigger ("Usar cuando hace falta el contexto completo de UNA tarea") plus the alternative and why it differs (get_tasks also carries the description but the list is noisier). It also routes the comment-thread case to get_task_comments, so both the when and the when-not are covered.

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