Skip to main content
Glama

Список тарифов

get_tariff_list
Read-onlyIdempotent

Показывает все тарифы с ценами, периодами и тем, что в них входит. Нужен, когда упёрлись в «недоступно на текущем тарифе»: по этому списку видно, какой тариф решает задачу. Цены считаются с учётом текущего тарифа аккаунта — доплата при переходе уже учтена. Только чтение: оплатить или сменить тариф через ассистента нельзя, это решение человека.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_tariff_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesID workspace. Взять из workspace://list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the description is not needed for safety basics, yet it adds real context: prices are computed relative to the account's current tariff with the upgrade surcharge already included, and payment or plan changes cannot be performed through the assistant. The 'Только чтение' sentence restates the annotation, but the surrounding detail about pricing and human-only decisions earns the score.

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?

Sentences are front-loaded: what is returned first, then the triggering situation, then the pricing semantics, then the mutation boundary. Nothing is padded, though the read-only sentence partly duplicates the annotation and could be trimmed to just the payment/plan-change constraint.

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 one-parameter, read-only listing tool with no output schema, the definition covers what comes back (prices, periods, contents), why to call it, how prices are derived, and what it cannot do. The remaining gap is minor: no hint about ordering, currency, or whether the current tariff is flagged in the result.

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?

The single workspace_id parameter is fully documented in the schema, including how to obtain it from workspace://list, so the schema does the heavy lifting. The description adds no syntax, format, or behavioral detail about the parameter, which is the expected baseline at 100% coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb and resource: it shows all tariffs together with prices, billing periods, and included features. That is more specific than the title alone, but it never names the sibling get_workspace_tariff, so the boundary between 'all plans' and 'my plan' is left for the agent to infer.

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 gives an explicit trigger condition: use it when the user hits 'unavailable on current tariff', since the list reveals which plan resolves the task. It does not state exclusions or name a preferred alternative tool for the simple 'what is my plan' case, which keeps it 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