Skip to main content
Glama

List credit packs, the monthly plans and Enterprise

list_credit_offers
Read-onlyIdempotent

List what SHIP sells: the credit packs (credits, the price in US dollars before tax, which checkout adds for the buyer's location, and the price per credit), the monthly plans under team.plans (Starter and Scale: each its credits a month, monthly price, price per credit, which credits added on top also cost, and agents at once), the range of credits a workspace on a plan can add at once, Enterprise under enterprise (the minimum yearly credit commitment, the highest and lowest price per credit, and the agents at once at the minimum; contracts are sold by SHIP, not through checkout), what Free and the packs allow (limits), the trial size, and site hosting under sitesHosting (the price a month for each site without a monthly plan, or null where hosting is not on sale). The same catalog the pricing page shows.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotent, non-destructive, closed-world), so the description earns credit for adding behavior beyond them: checkout adds tax for the buyer's location, Enterprise minimums and per-credit ceilings are disclosed, and `sitesHosting` is explicitly null where hosting is not on sale. That null semantics and the checkout-tax note are exactly the kind of context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The whole definition is a single sprawling sentence built from nested parentheticals enumerating return fields, which is dense and hard to scan. The opening 'List what SHIP sells' is front-loaded, but the rest is a field dump rather than a structured breakdown. It is informative without much waste, yet the structure works against readability.

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 zero parameters, no output schema, and strong annotation coverage, the description does the main remaining work: enumerating what each section of the catalog returns, including units (US dollars before tax, price per credit, credits per month). The agent knows what to expect from the response. Only minor gaps remain, such as any error or empty-catalog behavior.

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 input schema is empty, so there are no parameters whose meaning needs elaboration; baseline 4 applies. The description correctly spends its budget on the shape of the result instead of inventing parameter detail.

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 a specific verb and resource: list what SHIP sells, broken down into credit packs, `team.plans`, `enterprise`, `limits`, trial size, and `sitesHosting`. An agent can tell this is a read-only pricing catalog. Sibling differentiation is only partial: it notes contracts are sold by SHIP rather than through checkout, which implicitly points at `start_credit_checkout` without naming it.

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: 'the same catalog the pricing page shows' suggests pre-purchase price lookup, and the note that Enterprise contracts go through SHIP rather than checkout is a partial when-not for the checkout sibling. There is no explicit instruction on when to call this versus `start_credit_checkout`, and no prerequisites are given.

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.