Skip to main content
Glama

Buy Data Credit or Action packs

spur_buy_credit_pack

Create a Stripe checkout link for metric packs at the account's current price. Adds dollars to the shared wallet; it does not increase monthly allowances or reserve units. Free accounts must upgrade. No charge occurs until the user pays on Stripe.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "metric_key": "<metric_key>",
      "pack_count": "<pack_count>"
    },
    "name": "spur_buy_credit_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
metric_keyYes
pack_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already mark this as a non-readOnly, non-destructive, open-world mutation; the description adds substantial context on top: a link is generated rather than a charge made, funds land in the shared wallet and do not raise allowances or reserve units, free accounts are blocked, and payment happens externally on Stripe. These are exactly the behavioral traits an agent needs and none are derivable from the annotations.

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?

Four short sentences, led by the action, followed by the ledger effect, eligibility gate, and charge timing. No filler or repetition; each sentence conveys a distinct constraint.

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 two-parameter external-payment tool with no output schema, the description covers the important unknowns: no immediate charge, wallet-vs-allowance effect, and eligibility. The remaining gap is that it never says the call returns a checkout URL for the user to visit, which would round out the picture.

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

Parameters2/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 carry parameter meaning and largely does not. It never explains that metric_key selects between data_credit and action packs, nor what pack_count means or that it is bounded 1–1000; 'metric packs at the account's current price' hints at pricing but not at the two enum values.

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?

States a specific verb and resource — 'Create a Stripe checkout link for metric packs' — and clarifies the ledger effect ('Adds dollars to the shared wallet; it does not increase monthly allowances'). That effect-level distinction separates it from plan-upgrade siblings like change_plan, though no sibling is named outright.

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?

Gives an explicit precondition ('Free accounts must upgrade') and clarifies that no money moves until the user pays on Stripe, which is the key decision context. It stops short of naming the alternative tool to use when an agent wants more allowance rather than wallet dollars.

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