Skip to main content
Glama

get_task_status

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. You can also pass message to leave a note for the operator in the same call.

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
messageNoOptional note to the operator (stored on the record).
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?

With no annotations, the description carries the burden and does so reasonably: it discloses that output is brief by default with an opt-in full record, that tasks require an access_token obtained from request_quote, and that passing message writes a note to the record — a hidden side effect on an otherwise read-looking tool. It still omits error behavior for a mismatched id type or what 'brief' actually contains.

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 short sentences, front-loaded with purpose, then the full flag, then the auth requirement and the optional note. Every clause conveys actionable information with no padding.

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?

No output schema exists, so the description's brief/full distinction usefully sketches return shape, and it covers auth and the side-effecting message parameter. For a four-parameter tool it is nearly complete, missing only failure modes and detail on what the brief versus full payload includes.

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?

Schema coverage is only 50%, and the description compensates by explaining the two undocumented parameters: the id prefix convention identifying quote versus task, and the default/opt-in semantics of full. The message and access_token parameters already carry schema descriptions, so together every parameter has meaning.

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 ('Get the status of a quote or task') and disambiguates the identifier forms (quote_id q_… vs task_id t_…), so an agent knows exactly which records it can target. It is clearly a read-status lookup, distinct from siblings like get_evidence or accept_quote.

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 concrete conditions: default is the brief form, use full: true for the complete record, and access_token is required when the id is a task. It does not state exclusions or when to prefer a sibling tool, but the calling conditions are 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.

Resources