Skip to main content
Glama

sn_a2a_get_task

Read-only

Retrieve the status and result of an A2A task using its task ID and agent, so you can check progress or fetch completed output after sending a message.

Instructions

Get the status and result of an A2A task started with sn_a2a_send_message.

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": {
      "agent": "<agent>",
      "task_id": "<task_id>"
    },
    "name": "sn_a2a_get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesAgent sys_id or name
task_idYesTask id from the earlier reply

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that both status and result are returned, but says nothing about whether the call blocks, what status values are possible, or what happens if the task is still running.

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?

A single front-loaded sentence with zero filler; every phrase ('status and result', 'started with sn_a2a_send_message') carries information an agent can act on.

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?

For a simple two-parameter read tool with an annotation-covered safety profile, the definition is adequate but thin. It omits return-shape hints and polling behavior, which matter for an asynchronous task-status tool with no output schema.

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%, so both parameters (agent, task_id) are already documented in the schema. The description adds no format or sourcing detail beyond what the schema states, 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?

The description pairs a specific verb ('Get') with a specific resource ('status and result of an A2A task') and ties the tool to its producer, sn_a2a_send_message. That pairing lets an agent distinguish it from the send tool, though it does nothing to separate it from the unrelated generic task tools also present in the catalog.

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?

Usage is implied rather than stated: the phrase 'started with sn_a2a_send_message' tells the agent the precondition for calling it. There is no guidance on when not to call it, whether to poll repeatedly, or how it relates to sn_a2a_send_message for a fresh request.

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

Deploy Server

Other Tools