Skip to main content
Glama

Car Background AI

List subscription plans

list_plans
Read-only

List the subscription plans on offer, to quote prices or to get the price_id that create_checkout (workspace without a subscription) and change_plan (existing subscription) take. Each plan has its monthly photo allowance (credits), billing interval and price: unit_amount is in the smallest unit of currency (USD), and currency_options lists the fixed local prices whose keys create_checkout accepts as currency. Read-only and free; takes no parameters and is the same for every caller. It does not show the workspace's own balance: use get_credits for that.

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

A4.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly, non-destructive, closed-world) it adds that the call is free, takes no parameters, and returns identical results for every caller — genuinely useful for caching and for reasoning about auth scope. It does not discuss any failure modes or ordering guarantee, but for a static catalog read that gap is small.

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?

Purpose and the price_id hand-off are front-loaded, and no sentence is filler. The second sentence is dense enough that it packs several field definitions (credits, unit_amount units, currency_options keys) into one long clause, which slightly hurts scannability.

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?

There is no output schema, and the description compensates by documenting the returned fields an agent must act on: `credits` as monthly photo allowance, billing interval, `unit_amount` in the smallest unit of `currency`, and `currency_options` whose keys map to create_checkout's `currency` argument. Combined with the explicit exclusion of balance data, an agent has everything needed to call and consume it correctly.

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 has zero parameters, so per the baseline this starts at 4. The description instead spends its words on return-field meaning, which does not change the parameter score but is the right allocation here.

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

Purpose5/5

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

Opens with a specific verb+resource ("List the subscription plans on offer") and immediately names the two sibling consumers, create_checkout and change_plan, so an agent can tell what this tool feeds. It also explicitly separates itself from get_credits, which removes the most likely confusion with a credits-adjacent tool.

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

Usage Guidelines5/5

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

Gives concrete when-to-use triggers ("to quote prices or to get the `price_id` that create_checkout ... and change_plan ... take") and an explicit when-not ("It does not show the workspace's own balance: use get_credits for that"), naming the alternative directly. Nothing about invocation context is left to inference.

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