Skip to main content
Glama
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).

Turn automatic Energy top-up on or off

set_auto_top_up
Idempotent

Turn automatic top-up on or off. Turning it on authorizes future recurring charges to the subscription's saved card ($10 for 75 Energy whenever the balance falls below 50), so call it with enabled=true only after explaining the amount, threshold and recurring charges and getting the customer's explicit yes to those terms; a request to continue work or to buy one pack is not consent. Bring it up only when the customer asks how to avoid running out. enabled=false turns it off at once. A Team member's workspace is told the billing owner manages it, and one without a subscription card is told to add one. Charges nothing now. Returns whether top-up is on, the terms that apply 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": {
      "enabled": "<enabled>"
    },
    "name": "set_auto_top_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue turns automatic top-up on with the customer's explicit consent to recurring charges; false turns it off.
workspaceIdNoA 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

NameRequiredDescriptionDefault
actionYesAlways auto_top_up.
consentYesThe recurring-charge terms the customer agreed to, or null when top-up is off.
enabledYesWhether automatic top-up is on after this call.
messageYesWhat to tell the customer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, it discloses the financial consequences of enabling ($10 for 75 Energy below a 50 balance), the consent requirement, immediate disablement, team/member handling, and that nothing is charged now. These are exactly the behavioral details an agent needs before calling a billing-related mutation.

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?

The description is front-loaded with the action and consent condition, then adds the relevant edge cases without filler. Despite being dense, each sentence carries operational value for correct invocation.

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?

The tool is a billing-related mutation with an output schema and rich annotations. The description covers consent, side effects, special cases, and return guidance sufficiently; return values themselves need not be detailed because an output schema exists.

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 both parameters are already documented. The description still adds meaningful semantics for `enabled` by spelling out the recurring charge amount, threshold, and consent boundary, though it does not add much about `workspaceId` beyond the schema.

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 states a specific action and resource: turn automatic Energy top-up on or off. It also distinguishes consent to recurring top-up from buying a single pack, so an agent can tell it apart from sibling purchase behavior.

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?

It gives explicit when-to-use guidance: bring it up only when the customer asks how to avoid running out. It also gives when-not-to-use guidance by saying a request to continue work or buy one pack is not consent, and it requires explanation plus explicit yes before enabling.

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