Skip to main content
Glama
Sign In
@qirabot/mcp

@qirabot/mcp

by qirabot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_task

Retrieve the current status and step details of a running task. Includes action type, AI decision, params, and output for each completed step.

Instructions

Get the status and step details of a task started by run_task.

Returns current status and all completed steps with action type, AI decision, params, and output. Possible status values: pending, running, succeeded, failed, cancelled, timeout, partially_succeeded. If status is 'pending' or 'running', poll again (recommended interval: 2-3 seconds).

Screenshots are not included in the response — use take_screenshot after completion to verify the result.

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

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task ID returned by run_task

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, but description explains response structure (status, steps with details), lists possible statuses, and mentions polling interval and absence of screenshots. Discloses read-only behavior implicitly.

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?

Three succinct sentences: purpose, response details, and usage note. No unnecessary words; information is front-loaded.

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?

Given simple tool (one param, no output schema), description covers response, status values, polling, and a common follow-up action. No 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?

Only one parameter (task_id) with full schema description coverage (100%). Description does not add further value beyond what the schema already provides.

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?

Description clearly states verb 'get' and resource 'status and step details of a task', linking it to 'run_task'. Distinct from siblings like run_task, cancel_task, and take_screenshot.

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

Usage Guidelines4/5

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

Describes when to use (after run_task), provides polling guidance for pending/running status, and notes that screenshots require take_screenshot. Lacks explicit 'when not to use' but sufficient for this tool.

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