Skip to main content
Glama

Make a top-up pay link for my owner

top_up

Create a payment link to fund your balance; it buys nothing (to get an item, use buy; a first site check badge: buy_site_badge). Give pay_link to your human owner: it works for 7 days; they tick a box to agree to the waiver, then pay on Stripe's page (USD). Humans always use pay_link. Only for a machine payment by your own agent wallet: set for_agent_wallet: true to also get url, the direct Stripe page (about 30 minutes). Then poll top_up_status with its topup_id.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount_cents": 500
    },
    "name": "top_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_centsYesHow much to add to your balance: 500, 1000, 2000, 5000 or 10000 US cents.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.
for_agent_walletNotrue only when your own agent wallet pays (machine payment): the answer then also holds url. Never give url to a human.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / amount_cents / description
      Previous value: -"500, 1000, 2000, 5000 or 10000 US cents."New value: +"How much to add to your balance: 500, 1000, 2000, 5000 or 10000 US cents."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "amount_cents": 500
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Changed2 schema fields changed
    • changedInput schema / properties / amount_cents / anyOf
      Previous value: -[
      -  {
      -    "const": 500,
      -    "type": "number"
      -  },
      -  {
      -    "const": 1000,
      -    "type": "number"
      -  },
      -  {
      -    "const": 2000,
      -    "type": "number"
      -  }
      -]New value: +[
      +  {
      +    "const": 500,
      +    "type": "number"
      +  },
      +  {
      +    "const": 1000,
      +    "type": "number"
      +  },
      +  {
      +    "const": 2000,
      +    "type": "number"
      +  },
      +  {
      +    "const": 5000,
      +    "type": "number"
      +  },
      +  {
      +    "const": 10000,
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / amount_cents / description
      Previous value: -"500, 1000 or 2000 US cents."New value: +"500, 1000, 2000, 5000 or 10000 US cents."
  5. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / amount_cents / description
      Added value: +"500, 1000 or 2000 US cents."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  6. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnly=false, openWorld=true, idempotent=false, destructive=false; the description adds real behavioral detail beyond them — the link expires in 7 days, the owner must tick a waiver box, payment occurs on Stripe in USD, and url is short-lived (~30 minutes). It stops short of noting whether repeated calls create duplicate links (relevant given idempotentHint=false), so it is not a 5.

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 critical constraint (this buys nothing; use buy instead) is front-loaded and no sentence is filler, but the semicolon-and-parenthetical style makes it denser than necessary for a two-branch workflow.

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?

With no output schema, the description still tells the agent what it gets back (pay_link, optionally url, and a topup_id) and what to do next, plus the human-versus-machine split. That is complete for a link-creation tool of this complexity.

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 the baseline is 3, but the description adds operational meaning the schema does not: for_agent_wallet is framed as the machine-payment branch and paired with the ~30-minute url lifetime and the instruction not to hand url to a human. passport_token is left entirely to the schema, which is a minor gap.

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?

Opens with a specific verb and resource: "Create a payment link to fund your balance." It immediately disambiguates from siblings by naming buy and buy_site_badge and stating that this tool "buys nothing," so an agent can distinguish it without inspecting other 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?

Explicit routing rules are given for both branches: humans use pay_link, and only machine payments by the agent's own wallet set for_agent_wallet: true. It also names the follow-up tool (top_up_status with topup_id) and the alternative purchase tools, leaving nothing to inference.

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.