Skip to main content
Glama

Birinchi Shop — Uzbekistan store

Order status

get_order_status
Read-onlyIdempotent

Status of an order placed earlier. Requires the order id and the last 4 digits of the customer's phone.

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": {
      "order_id": "<order_id>",
      "phone_last4": "<phone_last4>"
    },
    "name": "get_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesOrder id returned by place_order.
phone_last4YesLast 4 digits of the phone number used for the order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / order_id / description
      Added value: +"Order id returned by place_order."
    • addedInput schema / properties / phone_last4 / description
      Added value: +"Last 4 digits of the phone number used for the order."
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds one genuine behavioral detail beyond the schema: the phone last-4 acts as a verification gate for accessing order data. It does not describe failure behavior (wrong order id or mismatched phone) or what the response contains.

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 short sentences, no filler, with the resource stated first and the required inputs second. Nothing is padded, though the second sentence duplicates information already in the schema.

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?

With no output schema, the description carries the burden of explaining what a "status" response contains, and it does not. For a simple two-parameter read tool with rich annotations this is a modest gap rather than a blocking one, but an agent cannot predict the return shape.

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 description coverage is 100%, with both order_id and phone_last4 documented including the pattern constraint and the cross-reference to place_order. The description only restates those parameters rather than adding format, provenance, or error semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (an order placed earlier) and implies a lookup verb, but "Status of an order" largely restates the name and title without defining what status means (shipping stage, payment state, fulfillment). An agent knows it is a read on an existing order but not what information it will receive.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus siblings like get_product or search_products, nor any note on preconditions such as an order having been placed first. The only usage signal is the implicit "requires" phrasing about parameters, which the schema already enforces.

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