Skip to main content
Glama

Extreme Drive — extreme driving school

Статус заказа

get_order
Read-only

Статус заказа по непрозрачному order_id из create_order: awaiting_payment, paid, accepted_manager_will_call, expired. Без персональных данных. Если заказ ещё не оплачен и это не courier, возвращает payment_url.

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>"
    },
    "name": "get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesНепрозрачный идентификатор из create_order

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 readOnlyHint=true and openWorldHint=false, so safety is covered. The description goes further by disclosing that no personal data is returned, that statuses are a fixed set, and that payment_url is returned conditionally (unpaid and not courier) — real behavioral context beyond the annotations. The 'не courier' condition is left unexplained, which keeps it from 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.

Conciseness5/5

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

Three short sentences, front-loaded with the core purpose, then the status enumeration, then the return behavior. Nothing is padded and each sentence carries distinct information.

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 no output schema, the description does the necessary work of naming the status values and the conditional payment_url, which is what an agent needs to interpret the response. It stops short of covering error cases such as an unknown or expired order_id, which would round out a read-only lookup tool.

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?

With a single parameter at 100% schema coverage, the schema already documents order_id as an opaque identifier from create_order. The description restates the same fact rather than adding format, validation, or lookup semantics, so the baseline of 3 applies.

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

Purpose5/5

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

The description states a specific verb and resource (order status by order_id) and immediately ties the identifier to its origin in create_order, which separates it cleanly from the sibling create_order and the list_* tools. It even enumerates the possible status values, so an agent knows exactly what this call yields.

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?

The reference to 'order_id из create_order' establishes the usage flow: call this after creating an order to poll its state. There are no explicit exclusions or named alternatives, but the sibling set contains no other status-lookup tool that would need disambiguation.

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