Skip to main content
Glama

list_credit_packs

Browse available credit bundles and their current pricing. Use this to help the user choose the best pack for their "purchase_credits" call.

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

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. It implies a read-only browse that returns bundle names and current prices, which is the key behavioral fact, but it says nothing about pagination, currency, whether prices are live vs. cached, or whether authentication/account context affects results. For a zero-parameter listing read the risk is low, so a 3 is fair rather than harsh.

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?

Two short sentences with the purpose front-loaded and no filler. The nested quoting around "purchase_credits" is slightly awkward but does not impede comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter listing tool with no output schema, the description covers what the tool returns at a high level (bundles and pricing) and its role in the purchase flow. It omits how results are shaped or whether the list is filtered by account eligibility, which an agent might need to interpret the response.

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 no parameters and the schema has no properties, so there is no parameter meaning to convey; the baseline for 0 params applies. Nothing in the description conflicts with the empty schema.

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?

"Browse available credit bundles and their current pricing" gives a specific verb (browse) and resource (credit packs/pricing), which clearly separates it from get_credit_balance and purchase_credits. It stops short of explicitly stating scope (e.g., all packs vs. only ones available to this account), so it is clear but not maximally differentiated.

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

Usage Guidelines4/5

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

The second sentence gives concrete usage context: use it to help the user choose a pack before a purchase_credits call, which names the relevant sibling and the sequence of use. It does not state when not to use it (e.g., for balance checks use get_credit_balance), but the guidance is actionable.

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