Skip to main content
Glama

AceRound AI Interview Copilot

check_order_status

Read-only

Check whether an order has been paid and fulfilled. Use it after the user pays at checkout; PAID means the purchase is on the account. (Requires the user's sign-in with scope account:read.)

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": {
      "orderNumber": "<orderNumber>"
    },
    "name": "check_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNumberYesOrder number returned when the order was created, or from the recent orders in get_account

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a safe, closed read (readOnlyHint true, destructiveHint false, openWorldHint false), and the description adds context the annotations cannot: the call requires the user's sign-in with the account:read scope. It also clarifies the semantics of the PAID state, but says nothing about failure modes such as an unknown or malformed order number.

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?

Two compact sentences with the core action front-loaded and the auth prerequisite clearly bracketed as a parenthetical. No filler, though the PAID explanation could be merged more tightly with the main clause.

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 one-parameter read tool with annotations covering safety, the description supplies the two things an agent most needs: when to call it and the authorization prerequisite. There is no output schema, and the shape of the response beyond the PAID flag (e.g. fulfillment details) is left unstated, which is the main remaining gap.

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?

Schema coverage is 100% and the single orderNumber property already documents its origin (creation response or get_account recent orders) and length bounds. The description adds no further meaning about format or validation, so the baseline applies.

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 description names a specific verb and resource ('Check whether an order has been paid and fulfilled') and defines the key result token PAID. It implicitly separates the tool from create_payment_order by describing a post-payment verification step, but never names that sibling explicitly.

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?

'Use it after the user pays at checkout' gives a clear triggering condition tied to the purchase flow. It stops short of stating exclusions or naming which tool to call instead when the order does not yet exist, so it is strong context rather than full routing guidance.

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