Skip to main content
Glama
A1 Yandex KIT MCP

A1 Yandex KIT MCP

List alerts

list_alerts
Read-only

Retrieve paginated store system alerts, critical and newest first, filter by ACTIVE or RESOLVED status, and use coverage metadata to flag partial results instead of claiming completeness.

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_alerts"
  }
}

Input 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. Changed1 schema field changedv1.14.1
    • addedInput schema / properties / status / minItems
      Added value: +1
  2. 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"
      +}
  3. First observedv1.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantial behavior beyond that: pagination semantics, ordering guarantees, the default status filter, the shape of the coverage envelope, and an explicit agent obligation that coverage:"partial" must be surfaced and forbids claiming completeness. That is exactly the kind of operational and output-trust context annotations cannot carry.

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, front-loaded with what the tool returns and its ordering, then the calling constraint, then the response-contract warning. No filler, and the most important caveat (partial coverage) is placed last as a hard rule rather than buried.

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?

There is no output schema, so the description correctly compensates by naming the envelope fields (coverage, received, total_count, pages_read) and explaining how to interpret a partial result. For a six-parameter, read-only list tool with full schema coverage, nothing an agent needs to call or report it correctly 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% and every parameter is documented there, including the status default, per_page clamping, the all/pagination interaction, and csv fields. The description echoes the status default rather than adding new parameter meaning, so the baseline 3 applies.

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 gives a specific verb and resource ("List system alerts of the store") plus the sort contract (CRITICAL first, newest first within the same severity) and the paginated nature. An agent knows exactly what it gets back, which distinguishes it from other list_* siblings operating on blogs, orders, products, etc.

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?

It states a concrete calling constraint — the API requires a status filter, which defaults to ACTIVE — so the agent knows the tool works without arguments but is implicitly scoped to active alerts. No explicit when-not-to-use or alternative is named, but there is no competing alerts tool among the siblings to route away from.

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