Skip to main content
Glama

Migawari

Get task status

get_task_status
Read-only

Get the status of a quote or task by id (quote_id q_… or task_id t_…). Brief by default; pass full: true for the complete record. For tasks, the access_token is required. To leave a note for the operator, use 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": {
      "id": "<id>"
    },
    "name": "get_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
fullNo
access_tokenNoRequired for task ids; the token returned by request_quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true/destructiveHint=false, so the description's job is to add context, and it does: it discloses the default brief response versus the full record and the task-specific authentication requirement. It doesn't cover failure behavior for invalid or unknown ids, which is the main remaining gap for a lookup tool.

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 tight sentences with zero filler, front-loaded with the purpose and id formats before the parameter behavior and the sibling redirect. Every clause carries usable information.

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?

For a 3-parameter read-only lookup with no output schema, the description supplies the default response shape (brief) and the opt-in shape (full record), plus the auth precondition for task ids. Only edge-case details such as invalid-id errors or what fields 'brief' returns are left unspecified, which is minor here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 33% schema description coverage, the description must compensate, and it adds real meaning for all three parameters: the accepted id prefixes, the brief-vs-full semantics of the full flag, and the fact that access_token applies only to task ids. It stops short of explaining what the full record contains or token failure behavior, so it isn't exhaustive.

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 (get status) and resource (quote or task), and spells out the id formats (q_… for quote_id, t_… for task_id) so an agent knows both variants it accepts. It also distinguishes itself from the sibling send_message, which is named as the way to leave a note rather than fetch status.

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?

Gives an explicit selection rule for the full parameter (brief by default, pass full: true for the complete record) and a precondition (access_token required for task ids). It also redirects note-leaving to send_message. It doesn't address when to prefer this over other read siblings like get_evidence, but the core when/when-not guidance is clear.

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.