Skip to main content
Glama
ztemerbekov

A1 Yandex KIT MCP

by ztemerbekov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get order

get_order
Read-only

Retrieves a single order by ID, including line items, delivery chunks, payment, and status. Use redact:true to replace personal data with [redacted] when order details don't require it.

Instructions

Get a single order by its ID, including line items, delivery chunks, payment and status. Read the delivery address from delivery_chunks[].delivery_info.address.locality/.address: they always match the chosen delivery method, while the courier_*, pickup_point_* and self_pick_up_* groups keep whatever the buyer picked earlier in checkout and are stale unless the group matches method.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOrder ID (UUID).
redactNoUse redact:true when the task does not need personal data (e.g. counting or aggregating orders) — personal fields (name, phone, email, delivery address and its parts, notes) are replaced with "[redacted]". Applies to the response only; request bodies are never redacted. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / redact
      Added value: +{
+  "description": "Use redact:true when the task does not need personal data (e.g. counting or aggregating orders) — personal fields (name, phone, email, delivery address and its parts, notes) are replaced with \"[redacted]\". Applies to the response only; request bodies are never redacted. Default false.",
+  "type": "boolean"
+}
  2. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint=true already signals a safe read, and the description adds non-obvious behavior: the delivery_chunks[].delivery_info.address fields are authoritative while the courier_*, pickup_point_*, and self_pick_up_* groups may be stale unless they match `method`. This is valuable context beyond the annotations.

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?

Two sentences, front-loaded with the core purpose, and the second sentence earns its place by warning about a real data-consistency trap. No filler or redundant restatement of the schema.

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?

The description covers the key included order components and the main field-nuance an agent needs to interpret the response. It omits explicit return formatting or error cases, but the tool is a simple read-by-ID operation and no output schema exists to fill those gaps.

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%, so the schema already documents id and redact fully. The description adds no parameter-level detail beyond the schema, which is acceptable but does not elevate the score above baseline.

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: get a single order by ID, and lists returned components (line items, delivery chunks, payment, status). This clearly distinguishes it from list_orders and order-related sibling tools like get_order_delivery_labels or get_order_addons.

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

Usage Guidelines3/5

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

The description implies use when fetching one full order by ID, but it does not explicitly contrast with sibling order tools such as get_order_delivery_labels, get_order_addons, or list_orders. The stale-address guidance is useful data semantics, not usage routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools