Skip to main content
Glama

Deposit by card

create_wallet_deposit

Creates a Stripe Checkout URL a human must open to pay. Wallet is credited on payment.

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_cents": "<amount_cents>"
    },
    "name": "create_wallet_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_centsYes
workspace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations only flag that this is a non-destructive write, but the description adds genuinely useful behavior: the tool does not move money itself, it returns a URL a human must open, and the wallet is credited only after payment. That two-phase asynchronous contract is exactly what an agent needs. It still omits what happens to duplicate/abandoned checkouts, which matters given idempotentHint=false.

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?

Two short sentences, front-loaded with the action and then the outcome. Nothing is padded and each clause carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no output schema, the description covers the core flow but leaves gaps an agent needs: whether the Checkout URL is the returned value and how to present it, the unit/currency of the amount, and whether repeated calls create multiple payable URLs.

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 it does not. It never states that amount_cents is in cents, what currency or minimum applies, or what workspace_id selects; the only hint is the general notion of an amount being paid.

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?

The description names a specific verb and resource (creates a Stripe Checkout URL for a wallet deposit) and specifies the mechanism, which implicitly separates it from the crypto/x402 sibling. It does not explicitly name an alternative, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'a human must open to pay' tells the agent this is for interactive card payment, and the wallet-credit note hints at the follow-up. There is no explicit when-to-use, when-not-to-use, or named alternative such as create_x402_deposit for non-card deposits.

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.