Skip to main content
Glama

Тариф аккаунта

get_workspace_tariff
Read-onlyIdempotent

Возвращает тариф аккаунта целиком: код тарифа, оплачен ли он, сколько дней осталось, все лимиты с остатками (опросы, ответы, участники, темы, место на диске, адреса для писем) и список возможностей — свой домен, своё хранилище, роли, выгрузка ответов, публичные ссылки, AI-отчёт, интеграции. seats — если участников больше, чем мест в тарифе: сколько мест, сколько занято, до какого дня у лишних доступ и offer — как уместить всю команду; мест хватает — null. Смотрите сюда, когда действие отклонено «по тарифу»: здесь видно, кончился лимит, истёк срок или возможности нет вовсе. Только чтение — смена тарифа и оплата не через ассистента.

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_workspace_tariff"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real content by explaining that seats is populated only when members exceed seats, what it contains (count, occupied, access end date, offer), and that it is null when seats suffice. The 'только чтение' note and the explicit statement that changing the plan or paying are not available through the assistant reinforce the safety profile with scope information the annotations do not express.

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?

It is front-loaded with the return summary, then moves to the conditional seats/offer behaviour and finally to the usage trigger, which is a sensible order. The long parenthetical enumerations of limits and features are dense but each item maps to real payload content that has no output schema to document it; slight tightening would help but nothing is filler.

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?

With no output schema, the description carries the entire burden of describing the response, and it does so thoroughly, including the non-obvious nullable seats field and its nested meaning. Combined with the single fully documented parameter and the already-rich annotations, an agent has everything needed to call it and interpret 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?

There is a single parameter and schema description coverage is 100%, with the schema already stating it is the workspace ID sourced from workspace://list. The description adds nothing about workspace_id, so the baseline 3 applies when the schema carries the full burden.

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+resource ('Возвращает тариф аккаунта целиком') and then enumerates exactly what the payload carries: code, payment status, days left, limits, features, plus the special 'seats' and 'offer' fields. An agent knows precisely what comes back. It loses the top mark only because it never distinguishes itself from adjacent reads such as get_tariff_list or get_workspace_storage_usage.

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 a concrete trigger condition: use this when an action was rejected 'по тарифу', because here you can see whether a limit ran out, the term expired, or the feature doesn't exist. It also marks the boundary of scope ('смена тарифа и оплата не через ассистента'). No sibling alternative is named for the case where the agent wants a catalog of plans rather than the current one, so a named-alternative routing is missing.

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