Skip to main content
Glama
ztemerbekov

A1 Yandex KIT MCP

by ztemerbekov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List alerts

list_alerts
Read-only

Get paginated store alerts with critical first and newest within each severity. Filter by status (defaults to active) and respect partial coverage responses to avoid claiming a complete list.

Instructions

List system alerts of the store (paginated), CRITICAL ones first and newest first within the same severity. The API requires a status filter; defaults to ACTIVE when not provided. 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.
statusNoFilter by alert status (default: [ACTIVE]).
per_pageNoItems per page, 1-100 (default 25). 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/5.0
Behavior5/5

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

The readOnlyHint annotation already signals safety, and the description adds substantial behavioral context beyond it: CRITICAL-first ordering, newest-first within severity, pagination semantics, and the machine-readable coverage envelope. The explicit instruction that partial coverage must be reflected in the user-facing answer is especially valuable.

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 dense sentences, each adding necessary information: listing behavior and ordering, API filter default, and response coverage semantics. There is no filler, and the most identifying information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list operation with no output schema, the description covers the essential invocation and interpretation details: pagination, ordering, default filtering, and the coverage envelope with a normative rule for partial results. The parameter schema fills in the remaining input details, so no critical information 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%, so the parameters themselves are already fully documented. The description mostly restates or reinforces what the schema already says, such as the ACTIVE default, without adding new parameter-level meaning beyond the schema.

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 opens with a specific verb and resource — "List system alerts of the store" — and adds precise behavioral detail: pagination, severity ordering, and newest-first ordering within severity. This makes the tool clearly distinguishable from mutation siblings like resolve_alert and from other list_* tools.

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 description gives clear context on how the listing behaves: it is paginated, sorted, defaults its status filter to ACTIVE, and can return partial coverage. It does not explicitly name an alternative for changing or resolving alerts, so the guidance is clear but not exhaustive.

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