PumpGTM

This connector has been deprecated

Duplicate listing. The official PumpGTM connector is https://glama.ai/mcp/connectors/com.pumpgtm/mcp (same server, https://mcp.pumpgtm.com/mcp).

Get a payment link for Energy

buy_energy

Get a payment link to buy Energy packs, only after the customer agrees to the amount (offer the smallest top-up from energy's refill guidance). Nothing is charged by this call: the customer opens checkoutUrl and pays; Energy lands within a minute of payment and lasts twelve months. Recheck the balance with energy after payment before resuming work. A workspace without a saved card is told how to add one, and a Team member's workspace is told the billing owner buys. This never turns on automatic top-up; set_auto_top_up does that with its own consent. Returns packs, energy, usd, checkoutUrl and a message to relay.

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": {
      "packs": "<packs>"
    },
    "name": "buy_energy"
  }
}

Input Schema

Name	Required	Description	Default
`packs`	Yes	Packs to buy; each pack is $10 for 75 Energy, or 100 Energy each when buying 5 or more. The billing page offers 1 ($10), 5 ($50), 10 ($100), 25 ($250), 50 ($500).
`workspaceId`	No	A teammate's workspace you may manage: an active workspace ID from list_team_workspaces. Omit for your own workspace. Supply on every call for a teammate.

Output Schema

Name	Required	Description
`usd`	Yes	Price in US dollars.
`packs`	Yes	Packs in the checkout.
`action`	Yes	Always buy.
`energy`	Yes	Energy the customer receives after paying.
`message`	Yes	What to tell the customer; nothing has been charged yet.
`checkoutUrl`	Yes	Payment link the customer opens to pay; share it as is.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond annotations: clarifies that nothing is charged by the call, that payment happens via checkoutUrl, that Energy arrives within a minute and lasts twelve months, and that the tool cannot enable auto top-up. It also discloses two failure branches — no saved card and a Team member's workspace where the billing owner buys.

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?

Front-loaded with the core action and precondition, and nearly every sentence carries operational content. It is somewhat dense with several clauses in one paragraph, but there is little filler.

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?

Covers consent gating, pricing behavior, latency, expiry, post-payment verification, and edge cases like missing payment methods and Team workspaces. Returns are summarized even though an output schema exists, leaving no gap for correct invocation.

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%, so pricing details for packs are already in the schema. The description still adds decision-level meaning by instructing the agent to pick the smallest top-up from energy's refill guidance, which the schema alone does not convey.

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?

States a specific verb and resource ('Get a payment link to buy Energy packs'), plus the precondition ('only after the customer agrees to the amount'). It explicitly separates itself from set_auto_top_up and points to energy for balance checks, so an agent can distinguish it from siblings without opening schemas.

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?

Gives explicit when-to-use ('only after the customer agrees to the amount'), a decision rule for choosing the pack ('offer the smallest top-up from energy's refill guidance'), and clear exclusions ('never turns on automatic top-up; set_auto_top_up does that'). It also prescribes the follow-up ('recheck the balance with energy after payment before resuming work').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PumpGTM tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?