Skip to main content
Glama

Plans (tariffs)

list_plans
Read-onlyIdempotent

The tariff catalog: each plan's monthly price (USD, RUB), credits and briefs a period. A subscription is bought with subscribe (a LavaTop payment link the user opens and pays). No sign-in needed. [REST: GET /api/plans]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so safety and idempotency are covered structurally. The description's genuine additions are the auth posture (no sign-in) and the fact that the payment flow lives in a different tool. It says nothing about caching, rate limits, or whether the catalog is static, which for a zero-param public catalog is a minor but real gap.

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?

Three short sentences, front-loaded with what the catalog contains before the routing note. Little waste, though the bracketed REST endpoint is low-value to a calling agent, and the phrase 'credits and briefs a period' is slightly compressed to the point of ambiguity.

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?

No output schema exists, and the description compensates by enumerating the returned fields (price currencies, credits, brief counts), so an agent knows what to expect from the response. For a zero-parameter, read-only catalog this is nearly complete; only return shape details (array vs object, currency selection rules) are unstated, and those are minor here.

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?

The tool takes no parameters (schema is an empty closed object), which is the baseline-4 case. No per-parameter explanation is required, and the description adds no misleading pseudo-params.

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 names the resource precisely (the tariff catalog) and enumerates what each entry holds: monthly price in USD/RUB, credits, and brief counts per period. It also distinguishes this read of the catalog from the sibling that actually transacts ('A subscription is bought with subscribe'), so an agent can tell the two apart without opening either schema. The only shortfall is the absence of an explicit verb like 'list' or 'return', which is implied rather than stated.

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 clear selection context: use this to see prices/credits, and use subscribe when the goal is to actually purchase, since that is the tool that yields a payment link to open. 'No sign-in needed' is a useful precondition. There is no explicit 'do not use this for X' exclusion, 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