Skip to main content
Glama

Babelii-Diofis Account

Status pesanan

purchase_status
Read-onlyIdempotent

Pass exactly ONE of intent_id, order_number, order_id or track_url (two or none is refused). Use intent_id right after execute_purchase, order_number or track_url for a guest order. Any guest can check coarse status using their order_number. A full track_url from checkout unlocks guest details across sessions; never invent or fetch a tracking URL. An account or internal connection can use its own order_number or order_id. intent_id remains supported. Order creation is not delivery success.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "purchase_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idNo
intent_idNo
track_urlNo
order_numberNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the bar is lower; the description still adds real behavior: guest coarse status, track_url unlocking details across sessions, and the caveat that order creation is not delivery success. It doesn't describe behavior on unknown or ambiguous identifiers (e.g., not-found conditions), which keeps it below a 5.

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?

The most important constraint, the exclusive-one rule, is front-loaded, and the rest is dense and purposeful. Minor redundancy: intent_id is introduced early and then reintroduced with 'intent_id remains supported.'

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?

With an output schema present, return values needn't be explained, and the description covers the access-model complexity (guest vs. account vs. internal) that an agent would otherwise get wrong. It is only missing error/not-found expectations for a status lookup.

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 carry all meaning, and it does: mutual exclusivity (exactly one, two or none refused), provenance for each identifier, and the access level each unlocks. It still doesn't give value formats (order_number shape, what a valid track_url looks like) beyond 'from checkout'.

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 makes clear this retrieves order/purchase status and enumerates the four identifiers that can address an order, with the exclusive-one rule stated up front. It stops short of positioning itself against siblings like inquire_purchase, but the resource and scope are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives per-identifier routing conditions: intent_id right after execute_purchase, order_number or track_url for guest orders, order_number or order_id for an account or internal connection. It also flags the satisfiable-state distinction (coarse status vs. full guest details) and warns never to fabricate or fetch a track_url.

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