Skip to main content
Glama

Субъекты по одному показателю

regions_by_indicator
Read-onlyIdempotent

Значения одного показателя по субъектам Российской Федерации с единицей измерения, медианой по стране и крайними значениями. Без параметра «субъект» возвращаются все 89 строк, с ним — значение субъекта на фоне страны. Пустое значение означает «не рассчитано», а не ноль; число субъектов без значения и причина идут в ответе рядом. Если витрина показателей не собрана, инструмент отвечает отказом, а не пустым списком. Сравниваются территории, а не организации.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "показатель": "<показатель>"
    },
    "name": "regions_by_indicator"
  }
}

Input Schema

NameRequiredDescriptionDefault
субъектNoКод субъекта (например 62) или его название.
показательYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds genuinely new behavior: empty values mean 'not calculated' rather than zero, the count of subjects lacking values and the reason are surfaced in the response, and the tool refuses rather than returning an empty list when the data mart is not assembled. This is exactly the extra context annotations cannot provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what the tool returns, then modes, then null/refusal semantics, then the territories/organizations boundary. Slightly dense with four clauses, but every sentence carries distinct information and none is wasted.

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 tool with no output schema, the description covers output shape (unit, median, extremes), null semantics, response metadata, and failure behavior, with annotations handling the safety profile. Nothing an agent needs to invoke it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (only 'субъект' is documented). The description compensates by explaining the two modes driven by 'субъект' — all 89 rows versus one subject against the country backdrop — which meaningfully extends the schema, though it adds nothing about the 'показатель' enum beyond what the schema lists.

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?

States a specific resource and scope: values of one indicator across RF subjects, with unit, country median, and extremes. It even draws a boundary against a sibling by noting that territories are compared, not organizations, so an agent can route between this and the organization tool without reading 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear usage context: without the 'субъект' parameter all 89 rows are returned, with it a single subject against the country. The 'territories not organizations' line is a routing hint. However, no sibling is named explicitly and there is no explicit when-not guidance, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources