Skip to main content
Glama

List plans

list_plans
Read-onlyIdempotent

[read-only] The plans flayr sells today: price (USD monthly, USD per year annual), monthly Embers, seats, brands, connected accounts and features. intervals lists what start_checkout accepts for each plan; checkout says how it is bought. (Wraps GET /api/v2/billing/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. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without the description. What the description adds is return content — the pricing units (USD monthly vs USD per year annual) and the per-plan fields such as Embers, seats and features — plus the underlying GET endpoint. That is useful behavioral context, but there is no output schema to compare against and no statement about whether prices are live/current or cached.

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?

Compact and front-loaded: the resource and its field set come first, then the two field-level hints (`intervals`, `checkout`), then the endpoint wrapper note. Every sentence carries information; the bracketed '[read-only]' tag duplicates the annotation but is a single token.

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?

With no input parameters and no output schema, the description carries the burden of explaining the return shape, and it does so at a reasonable level by naming the plan attributes. It stops short of a field-by-field contract, so an agent still cannot know exact types or whether the 'features' list is enumerated, but it is adequate for a simple zero-arg catalog read.

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 zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies the call is unfiltered and returns all currently sold plans.

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 (the plans flayr sells today) and enumerates the key attributes returned: price in USD monthly/yearly, monthly Embers, seats, brands, connected accounts and features. It does not open with an explicit verb like 'list', but the intent is unambiguous. It also positions this as the catalog that start_checkout draws from, which helps separate it from the checkout sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: `intervals` lists what start_checkout accepts and `checkout` says how a plan is bought, so an agent can infer this is the lookup to call before start_checkout. There is no explicit 'use this when…' or 'do not use for…' statement, and no mention that it takes no arguments.

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