Skip to main content
Glama

Data Candy: US business leads

Add credits

add_credits
Destructive

Start a credit top-up of $10 to $1,000. THIS SPENDS MONEY once a person pays. Returns a Stripe checkout link that a person must open; the credits arrive after payment and buy_leads then spends them. Needs an API key.

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": {
      "amount_usd": "<amount_usd>"
    },
    "name": "add_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_usdYesTop-up amount in US dollars, 10 to 1000.
idempotency_keyNoOptional. Send the same value when retrying after a timeout so you are never charged twice for one purchase.

Output Schema

NameRequiredDescriptionDefault
next_stepYes
amount_usdNo
expires_atNo
session_idNo
balance_usdNo
checkout_urlYesA person must open this page to pay.
url_elicitationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint and openWorldHint, but the description adds the crucial context those hints cannot convey: this only spends money once a human pays, it returns a Stripe checkout link that a person must open, and credits are delivered asynchronously after payment. The API-key requirement is also disclosed, which matters for a money-moving call.

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?

The description is front-loaded with the money-spending warning in capitals, then explains the checkout-link mechanics and auth need in three short clauses. Each sentence carries distinct information, though the trailing 'Needs an API key' is slightly abrupt and could have been folded into the flow sentence.

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?

For a payment-initiation tool with an output schema, the description covers everything an agent needs to avoid a harmful call: the amount bounds, the fact that a human must complete payment, the asynchronous credit delivery, and the auth requirement. Return-value details are correctly left to the output schema.

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 100%, so both amount_usd and idempotency_key are already documented, and the description only restates the dollar range that the schema enforces. It adds nothing about the optional idempotency key, which is the parameter most likely to be misused on retry. Baseline 3 is appropriate when the schema carries the parameter burden.

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 gives a specific verb and resource ('Start a credit top-up'), bounds it ('$10 to $1,000'), and distinguishes it from siblings by naming the downstream consumer, buy_leads. An agent can tell this apart from quote_leads or preview_leads without opening any schema.

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?

The credit-flow narrative ('the credits arrive after payment and buy_leads then spends them') makes clear when this tool is needed: before lead purchases that require balance. It does not explicitly route to a sibling such as account_status for checking an existing balance first, so the when-not guidance is implied rather than stated.

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