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 ID to view its status, balance, and purchase details. Use redact mode to exclude personal data when not 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, 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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description aligns with a safe read operation. It adds useful context about the response contents (status, balance, purchase info) but does not disclose potential error behavior or note that redact only affects the response—though the latter is documented in the schema.

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 states the action, target, and key response fields with zero wasted words. It is immediately scannable and efficient.

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-only single-resource retrieval tool with fully documented parameters and a readOnlyHint annotation, the description covers the essential behavior. It communicates the return payload shape well enough; only explicit guidance about when to prefer list_gift_cards is missing, which is a minor gap.

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 coverage is 100%, so both parameters are already well documented. The description adds no extra meaning beyond restating that the card is fetched 'by its ID' and mentioning redaction indirectly via personal data, so it does not elevate beyond the 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 uses a specific verb ('Get') and resource ('a single gift card by its ID'), and enumerates what is returned (status, balance, purchase info). This clearly differentiates it from sibling list_gift_cards and other get_* tools without requiring schema inspection.

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 usage: call this when you have a gift card ID and need one specific card's details, versus listing all gift cards. However, it does not explicitly mention list_gift_cards or state when not to use this tool, leaving the comparison to inference.

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