Skip to main content
Glama

Babelii-Diofis Customer Support

Status pesanan

order_status
Read-onlyIdempotent

Use exactly one selector. A bare order_number gives coarse status only. A full track_url copied from the customer's checkout page unlocks the details; never invent or guess one. order_id works only for a connected account that owns the order. Never ask for passwords, PIN or OTP.

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

Input Schema

NameRequiredDescriptionDefault
order_idNo
track_urlNo
order_numberNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered upstream. The description adds real value beyond that: the granularity of results depends on the selector, order_id has an ownership/connected-account prerequisite, and there is an explicit security instruction never to solicit passwords, PIN or OTP. It does not describe pagination or error behavior when an invalid selector is supplied.

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?

Four short sentences, the governing rule ('use exactly one selector') placed first, followed by per-selector conditions and a security caveat. Every sentence carries an actionable constraint; nothing is 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?

With an output schema present, the description need not explain return values, and the 'coarse vs details' distinction usefully frames what the output will contain. Given three optional parameters and a read-only, closed-world operation, the main remaining gap is what happens when zero or multiple selectors are passed and any failure modes for a bad track_url.

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 description coverage is 0%, so the description must carry the parameter burden, and it does: order_number yields coarse results, track_url must be copied verbatim from the customer's checkout page and unlocks details, order_id requires a connected account that owns the order. Only the concrete types/formats are left to the schema, which handles them adequately.

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 status via one of three selectors and that the selector determines the depth of the result ('coarse status only' vs 'unlocks the details'). A literal verb like 'retrieve' is never stated, so it relies on the reader inferring the purpose from the selector discussion, but the resource and effect 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 Guidelines4/5

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

Strong routing guidance: 'Use exactly one selector' plus a distinct condition for each of order_number, track_url and order_id, including the constraint that order_id 'works only for a connected account that owns the order'. It also warns against fabricating a track_url. It stops short of naming when a sibling such as ticket_status would be the better choice, so it is not a full 5.

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