Skip to main content
Glama

Get a payment link for credits

buy_credits

Returns a payment link for a credit pack (pack_s 50, pack_m 150, pack_l 500 credits) or a plan (creator, pro, business; month or year). The person opens it, confirms on a Product Aura page and pays in Stripe; nothing is charged by this tool. Works without an account too: then it returns a link per pack, and the page after payment shows an API key.

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
packNo
planNo
intervalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint=false and openWorldHint=true already declared, the description adds real context beyond annotations: nothing is charged by this tool, payment happens out of band on a Product Aura page via Stripe, and the unauthenticated path returns one link per pack with an API key shown post-payment. It does not explain why the tool is non-idempotent (e.g. whether each call mints a fresh link) — the one behavioral gap.

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 tight sentences, front-loaded with the return value and its variants, then the checkout mechanics, then the anonymous fallback — each sentence carries new information. Slightly dense phrasing around 'then it returns a link per pack' costs a little readability.

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?

The tool is a link-minting entry point with no output schema, and the description does well to sketch the returned link and the post-payment API key. But with 0% schema coverage and all three parameters optional, an agent still cannot tell what a bare call produces or whether plan/interval must be combined, leaving a real ambiguity for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does partially: it decodes pack_s/m/l into 50/150/500 credits and explains that interval is month or year. It leaves the critical semantics unstated — whether pack and plan are mutually exclusive, whether interval only applies to plan, and what a call with zero arguments (required parameters: 0) returns.

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 names a specific verb+resource ('Returns a payment link') and enumerates both purchasable shapes with their exact enum values (pack_s/m/l with credit counts, creator/pro/business with month or year). An agent can distinguish this from siblings like list_packs, estimate_cost, or auto_topup without opening the schema.

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: it describes the checkout flow and the no-account variant, which tells the agent when the tool applies. However, it never says when to prefer this over auto_topup or list_packs, and there is no mention of prerequisites or which combination of the optional parameters is valid.

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.