Skip to main content
Glama
ztemerbekov

A1 Yandex KIT MCP

by ztemerbekov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List promocodes

list_promocodes
Read-only

Filter and paginate store promocodes by ACTIVE or INACTIVE status, with partial-coverage reporting when the result list is incomplete.

Instructions

List promocodes of the store filtered by status (paginated). The status filter is required by the API. The response carries a machine-readable coverage envelope (coverage, received, total_count, pages_read); coverage:"partial" MUST be reflected in the user-facing answer and forbids claiming the listing is complete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoFetch all pages via auto-pagination, up to 500 items; ignores page/per_page.
pageNoPage number, starting at 1 (default 1).
fieldsNoCSV columns; only valid together with format:"csv". Field names are validated against the item schema of the operation's response — an unknown name fails with the list of allowed fields. Default: every top-level scalar field of the item.
formatNoOutput format: "csv" renders the items as RFC 4180 CSV (a leading "# coverage:" comment line, then the header row) instead of JSON — cheaper for wide exports. Default: JSON.
statusYesPromocode status to include (required).
per_pageNoItems per page, 1-25 (default 25). The live API rejects values above 25 for this endpoint even though the published spec allows 100; values outside the range are clamped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.6.0
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "CSV columns; only valid together with format:\"csv\". Field names are validated against the item schema of the operation's response — an unknown name fails with the list of allowed fields. Default: every top-level scalar field of the item.",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Output format: \"csv\" renders the items as RFC 4180 CSV (a leading \"# coverage:\" comment line, then the header row) instead of JSON — cheaper for wide exports. Default: JSON.",
+  "enum": [
+    "csv"
+  ],
+  "type": "string"
+}
  2. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

The readOnlyHint annotation already signals a safe read, and the description adds meaningful behavior beyond that: the status filter is required by the API, the response includes a coverage envelope, and 'coverage:"partial"' must be surfaced to the user and forbids claiming completeness. This is valuable operational disclosure not present in 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?

The description is two sentences with no filler. The primary operation is front-loaded, and the critical coverage-envelope constraint is stated concisely in the second sentence. Every clause earns its place.

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 6-parameter, read-only list operation with no output schema, the description covers the essential selection criteria, the required filter, pagination behavior, and the important response-coverage semantics. Parameters like per_page clamping and CSV specifics are already fully documented in the schema, so the description is sufficiently complete for correct invocation.

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 input schema already documents every parameter including status, pagination, CSV format, and field selection. The description adds context about the required status and pagination/coverage behavior, but it does not materially extend parameter-level semantics beyond the schema. Baseline 3 is appropriate.

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 clear verb and resource: 'List promocodes of the store', and adds the specific scoping dimension 'filtered by status (paginated)'. This distinguishes it from related siblings like get_promocode and other list_* tools without needing to open the schema.

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 makes the main use case clear: list promocodes by required status with pagination. However, it does not explicitly mention alternatives or when not to use this tool, such as using get_promocode for a single promocode. Usage is implied rather than explicitly contrasted with siblings.

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