Skip to main content
Glama

Estado de una tarea

get_agent_task
Read-onlyIdempotent

Read a GitHub Copilot cloud agent task's current status once by task ID, optionally specifying the repository, to check progress or completion.

Instructions

Lee una vez el estado de una tarea del agente de Copilot.

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_agent_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepositorio owner/name. Si se omite, se usa el guardado al lanzar o el endpoint de usuario.
task_idYesIdentificador de la tarea.

Output Schema

NameRequiredDescriptionDefault
repoYes
errorYes
stateYes
usageYes
branchYes
task_idYes
artifactsYes
created_atYes
updated_atYes
completed_atYes
pull_requestYes
resolved_modelYessessions[].model, tal como lo devuelve la API.
requested_modelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds one useful behavioral nuance — 'una vez' signals a non-blocking single read rather than a wait/poll operation. It says nothing about failure behavior for unknown or in-flight tasks, which is a gap but a minor one given the annotation coverage.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently sized, though the brevity borders on under-specification rather than crispness.

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

Completeness3/5

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

The tool is simple (two params, one required) and an output schema exists, so return values need not be described. However, with openWorldHint=true and a repo parameter that has fallback semantics, the description could say more about what it reaches and when to call it. It is minimally adequate but leaves real gaps.

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%, with both repo and task_id documented in the schema itself, so the schema carries the parameter burden. The description mentions neither parameter and adds no meaning about the repo fallback behavior or identifier format. 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?

States a specific verb and resource: 'Lee una vez el estado de una tarea del agente de Copilot'. An agent can tell this retrieves the state of a single agent task, distinct from create_agent_task or list_copilot_models by name alone. It does not explicitly contrast with those siblings, which keeps it at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives, nor any prerequisite guidance (for example, that a task_id must come from create_agent_task). The only implicit cue is 'una vez', which hints at a single read rather than a polling loop, but that is not framed as usage guidance.

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