Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Check Async Status

check_async_status

Retrieve the last status of an asynchronous request by request_id, so you can track completion after an async downgrade.

Instructions

Show the last status of an async request Args: request_id: required, returned by an async downgraded request to the mcp server

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": {
      "request_id": "<request_id>"
    },
    "name": "check_async_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Last status' usefully implies a non-blocking snapshot rather than a wait, but nothing is said about whether the operation is read-only, what status values exist, whether the eventual result must be fetched elsewhere, or how long statuses are retained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded with the purpose in the first clause, which is good. The inline 'Args:' block is a slightly awkward way to present one parameter and consumes half the description's length without much payoff.

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 one-parameter polling tool with no output schema, the core is present but thin. The description never characterizes what the returned status means or what an agent should do with each outcome, which is the main gap for a status-checking tool.

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 0%, so the description must compensate, and it does add real meaning beyond the bare schema: request_id is required and originates from a prior async downgraded request. It stops short of giving format or length details, but the provenance note is the key semantic an agent needs.

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: 'Show the last status of an async request.' An agent can tell it retrieves status rather than the result itself. It does not, however, distinguish itself from the sibling get_docuengine_request_status, which sounds functionally similar.

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 only implied: the request_id is 'returned by an async downgraded request to the mcp server,' which hints this is a follow-up call after an async submission. It never states when to call it versus alternatives, how often to poll, or what to do once the status is terminal.

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