Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Wait For Request

wait_for_request
Read-only

Polls a submitted business registry or PPSR request until it reaches a final or action-needed state, then returns the latest status, timeout flag, and poll count.

Instructions

Poll a request until it reaches a terminal (or action-needed) state, then return that status response.

kind: "lodgement" -> GET /status/{id} (company registration, ABN); "ppsr" -> GET /ppsr/searches/{id}; "business_name" / "business_name_renewal" / "asic_484" / "company_name_change" / "company_deregistration" / "asic_361" / "asic_362" / "asic_ra52" -> that endpoint's own /{id}/status path. Stops on: finished, rejected, validation failed, completed, failed, cancelled, "wating ASIC CC payment" (business name needs the payer to open the link), or any HTTP error. timeout_seconds max 600. Returns the last status plus {"timedOut": bool, "polls": n}. Registrations in the sandbox usually finish in seconds to a few minutes; live ASIC/ATO processing can take longer — prefer webhooks for production.

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

Input Schema

NameRequiredDescriptionDefault
kindNolodgement
request_idYes
poll_secondsNo
timeout_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses the full set of terminal states that halt polling, the 600-second timeout ceiling, and the returned envelope with timedOut and polls. Minor typo ("wating ASIC CC payment") slightly muddies the stop-condition list, and polling cost/rate behavior is not mentioned.

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

Conciseness4/5

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

Front-loaded with the core behavior, then the kind routing table, then stop conditions and return shape — a logical order. The endpoint mapping block is dense and the multi-line enum listing is bulky, but each line carries information an agent needs to pick the right kind.

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 polling tool with an output schema present, the description covers stopping conditions, timing expectations, the terminal payload, and kind routing — everything needed to call it correctly. The remaining gap is poll_seconds semantics and any indication of polling overhead.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the burden and largely does: it maps each kind enum value to its concrete endpoint path and states the timeout_seconds maximum of 600, which overrides the schema's 120 default with meaningful constraint context. Only poll_seconds lacks any added explanation.

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 opening sentence gives a specific verb and mechanism — "Poll a request until it reaches a terminal (or action-needed) state, then return that status response" — which is clearly distinct from a one-shot sibling like get_request_status. It never names a sibling explicitly, so differentiation is inferred from the polling behavior rather than stated.

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?

It states when not to use this tool ("prefer webhooks for production") and characterizes expected latency in sandbox vs live ASIC/ATO processing, which is real guidance for choosing it. It stops short of explicitly contrasting with a single-call status tool, leaving the alternative implicit.

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