Skip to main content
Glama
ztemerbekov

A1 Yandex KIT MCP

by ztemerbekov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get gift card

get_gift_card
Read-only

Retrieve a gift card by its UUID to check status, balance, and purchase details. Use redact:true to hide personal data when only aggregate or count information is needed.

Instructions

Get a single gift card by its ID, including status, balance and purchase info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGift card ID (UUID).
redactNoUse redact:true when the task does not need personal data (e.g. counting or aggregating orders) — personal fields (name, phone, email, date of birth, 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.8.0
    • changedInput schema / properties / redact / description
      Previous value: -"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."New value: +"Use redact:true when the task does not need personal data (e.g. counting or aggregating orders) — personal fields (name, phone, email, date of birth, delivery address and its parts, notes) are replaced with \"[redacted]\". Applies to the response only; request bodies are never redacted. Default false."
  2. 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"
+}
  3. First observedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already declares this a safe read, so the safety burden is off the description. The description adds what the payload contains (status, balance, purchase info), which is useful, but says nothing about the redact-to-anonymize behavior or any permission/rate concerns.

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?

A single front-loaded sentence that names the resource, the key parameter, and the return contents with no filler. Nothing needs to be trimmed.

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?

For a simple read tool with readOnlyHint annotations and a fully documented schema, the description covers the essentials. It omits any hint about the redact option and the list_gift_cards alternative, but no output schema exists and nothing critical for correct invocation is missing.

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%: the id semantics (UUID) and the redact flag's full behavior are documented in the schema. The description only echoes 'by its ID' and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (Get) and resource (gift card) with scope ('single ... by its ID') and previews the returned data (status, balance, purchase info). It does not distinguish itself from the sibling list_gift_cards, which an agent must infer from the singular/plural naming.

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?

No when-to-use guidance and no routing to alternatives. The obvious sibling list_gift_cards is never mentioned, so the agent gets no explicit signal for choosing single-fetch over listing.

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