Skip to main content
Glama

Credit packs and payment methods

list_credit_packs
Read-onlyIdempotent

See the credit packs you can buy and which payment methods are available right now: Stripe shared payment tokens, card checkout for your human, and x402 wallet payment. Read-only; to buy one, call buy_credits with its pack id. Use it when your balance from get_balance will not cover the treatments you plan.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it is read-only, it reflects payment methods available 'right now,' and it routes purchases to buy_credits. It does not discuss rate limits or pagination, but those are minor for a zero-parameter listing tool.

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

Conciseness5/5

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

Two compact sentences front-load what the tool shows and then give usage guidance. Every clause earns its place by naming the payment methods, the read-only nature, the purchase alternative, and the balance trigger.

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?

With no input parameters and no output schema, the description fully covers what an agent needs: it explains the listing's conceptual return (credit packs and payment methods), the read-only guarantee, and the follow-up action. Nothing essential is missing.

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 there is no parameter semantics to clarify. The baseline for zero parameters is 4, and the description appropriately does not invent parameter details.

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?

The description uses a specific verb ('See') and resource ('credit packs you can buy and which payment methods are available'), clearly distinguishing this read-only listing from the write action in sibling buy_credits. An agent can identify exactly what this tool returns.

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?

It explicitly states when to use this tool ('when your balance from get_balance will not cover the treatments you plan') and names the alternative action ('to buy one, call buy_credits with its pack id'). This gives both the trigger condition and the next step, leaving little 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