Skip to main content
Glama

Buy credits

buy_credits
Read-only

Credit packs with prices and a direct checkout link (crypto or card). Pass a pack id for just that pack. Free; works without a key too.

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": "buy_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
packNoPack id: mini, starter, growth, pro, enterprise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / pack / description
      Previous value: -"Pack id: mini, growth, pro, enterprise"New value: +"Pack id: mini, starter, growth, pro, enterprise"
    • changedInput schema / properties / pack / enum
      Previous value: -[
      -  "mini",
      -  "growth",
      -  "pro",
      -  "enterprise"
      -]New value: +[
      +  "mini",
      +  "starter",
      +  "growth",
      +  "pro",
      +  "enterprise"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / pack / description
      Previous value: -"Pack id: starter, growth, pro, enterprise"New value: +"Pack id: mini, growth, pro, enterprise"
    • changedInput schema / properties / pack / enum
      Previous value: -[
      -  "starter",
      -  "growth",
      -  "pro",
      -  "enterprise"
      -]New value: +[
      +  "mini",
      +  "growth",
      +  "pro",
      +  "enterprise"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / pack / description
      Previous value: -"Pack id: mini, starter, growth, pro, enterprise"New value: +"Pack id: starter, growth, pro, enterprise"
    • changedInput schema / properties / pack / enum
      Previous value: -[
      -  "mini",
      -  "starter",
      -  "growth",
      -  "pro",
      -  "enterprise"
      -]New value: +[
      +  "starter",
      +  "growth",
      +  "pro",
      +  "enterprise"
      +]
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description then adds genuinely non-obvious context: the output contains prices and a direct checkout link (crypto or card), that usage is free, and that no API key is required — important because the 'buy_credits' name would otherwise suggest a side-effectful purchase call. It does not explain what a checkout link does or what happens with an invalid pack id.

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?

Three short, front-loaded sentences with no filler; the return content comes first, then the parameter behavior, then the auth/cost note. The telegraphic phrasing ('Credit packs with prices...') is efficient but slightly clipped, costing a bit of polish rather than clarity.

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?

For a one-optional-param, no-output-schema tool this covers what an agent needs: what comes back (pack prices plus a checkout link), how the parameter filters, and that no key is needed. Only minor gaps remain, such as error behavior for an unrecognized pack id.

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?

Schema coverage is 100% and the enum is self-documenting, so baseline is 3. The description goes one step further by explaining the optionality semantics — omitting the pack returns all packs, supplying it returns only that one — which the schema's bare enum list does not convey.

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 makes clear the tool returns credit pack listings with prices and a checkout link, and that a pack id narrows the result to one pack. The verb is implied rather than stated ('Credit packs with prices...'), which leaves slight ambiguity against the tool name 'buy_credits' — it is a catalog/checkout-link lookup, not a purchase action — but the resource and return content are unambiguous and clearly distinct from the OSINT siblings.

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?

'Pass a pack id for just that pack' tells the agent when to supply the optional parameter versus omitting it. It also removes a common blocker with 'Free; works without a key too,' which signals the tool is callable with no auth setup. There is no explicit statement of when-not-to-use or any named alternative, but none of the siblings are plausible substitutes.

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