list_tariffsВозвращает актуальные purchasable-тарифы, цену, валюту, product_id и точное число ссылок каждого типа.
| Name | Required | Description | Default |
|---|---|---|---|
| geo | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's 'returns' is consistent. It adds context about 'purchasable' and 'current' tariffs and specific data fields, but does not disclose additional behavioral traits such as caching, pagination, or permission requirements. With annotations covering the safety profile, a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is front-loaded with the verb and lists the key return fields. It contains no fluff or redundancy, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Although an output schema exists and the description mentions some return fields, the description omits the meaning of the required 'geo' parameter, which is a critical gap. An agent cannot correctly invoke the tool without understanding how to set 'geo'. This makes the description incomplete for selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has zero description coverage for the only parameter 'geo', and the description does not mention it at all. Since schema coverage is 0%, the description must compensate, but it fails to explain what 'geo' means or how it affects the results. The enum values ('ru', 'intl') offer partial clues, but the description adds no semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns current purchasable tariffs with specific fields (price, currency, product_id, and exact link counts). The verb 'Возвращает' and resource 'тарифы' are specific, distinguishing it from sibling tools that handle orders, links, or donors.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. It does not mention sibling tools like list_links or list_orders, and the intended use case is only implied by the name and description rather than explicitly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but a few pairs (check_registration vs get_account_profile, submit_link vs submit_order) overlap in scope. Descriptions clarify the differences (single vs bulk, status vs full profile), so confusion is limited.
All tool names follow a consistent verb_noun pattern in snake_case (begin_registration, list_orders, update_link_draft). The only slight deviation is 'bulk_update_order_draft' with the 'bulk' modifier, but it still fits the overall pattern.
14 tools is well within the ideal range for a specialized service covering registration, orders, links, tariffs, and checkout. Each tool serves a distinct function without unnecessary bloat.
The core workflow (register, browse tariffs, manage order drafts, submit links) is well covered. Minor gaps like lack of explicit order creation or deletion are likely handled externally or via the checkout process, so agents can still complete key tasks.