Skip to main content
Glama

List prices

list_pricing
Read-onlyIdempotent

The price list. Read-only and free: nothing is created or charged. Returns every plan on sale (name, USD per month, credits per month, USD per credit), every one-time credit pack (credits, USD, USD per credit) and, when this account would get it at checkout, the first-purchase offer. Also returns what things cost in credits: a video, and each add-on or clip product that is switched on, with its credits per unit (per scene, or per second with the length range). account.usdPerCredit is what one credit costs this account in USD (usdPerCreditBasis says where the number comes from), so a credit price can be told to the user in dollars. All prices are what customers pay; tax may be added at checkout. Requires the "video:read" scope.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds real value: it states nothing is created or charged, that it is free, that the required scope is "video:read", and that all returned prices exclude tax which may be added at checkout. Those are exactly the caveats an agent needs before repeating a number to a user. It does not cover rate limits or pagination, but there is little left to disclose for a static catalog.

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?

The key facts are front-loaded ("The price list. Read-only and free: nothing is created or charged"), which is the right ordering. The middle sentence is long and packed with parenthetical field lists, pushing it toward density rather than bloat; almost every clause carries information, though the enumerations could be tightened.

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, so the description has to carry the return contract itself, and it does: it names the plan fields (name, USD per month, credits per month, USD per credit), the credit-pack fields, the optional first-purchase offer, and the per-unit credit pricing for video and add-ons. Combined with the scope requirement and tax caveat, an agent has everything needed to call this correctly and interpret the result.

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 the baseline applies and there is nothing for the description to disambiguate at the input layer. Instead it spends its words explaining the shape of the output fields (usdPerCredit, usdPerCreditBasis, credits per unit per scene or per second), which is useful but is a return-value concern rather than a parameter one.

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 framing ("The price list") and then enumerates exactly what is returned: every plan on sale, every one-time credit pack, the first-purchase offer, and credit costs for a video and each active add-on/clip product. That is far more specific than a name restatement. It stops short of explicitly naming a sibling such as quote_video or get_credit_balance, so the boundary between a static catalog and a computed quote is left implicit.

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: read-only, free, requires the "video:read" scope, so an agent can infer it is the lookup to call before quoting anything to a user. However, there is no explicit when-to-use/when-not guidance and no reference to alternatives like quote_video or get_credit_balance, which an agent must disambiguate on its own.

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