Skip to main content
Glama

Get fees

get_fees

The raw, sourced fee entries behind every answer: percent, fixed fee, caps, minimums, extras (international, instant payout, chargebacks), the source URL and the date verified. Filter by platform (stripe, square, paypal, venmo, cash_app, helcim, melio, payoneer, wise_business, shopify_payments, zelle, ebay, etsy, upwork, fiverr, amazon, quickbooks_payments, quickbooks_payments_desktop, freshbooks, wave, xero, gocardless, zoho_payments, bill_com, honeybook, bonsai, invoice2go, jobber, housecall_pro, toast, clover, godaddy_payments, wix_payments, squarespace_payments, lightspeed, sumup, paypal_pos, patreon, gumroad, kofi, buymeacoffee, substack, teachable, kajabi, podia, lemonsqueezy, paddle, fanfix, poshmark, mercari, depop, stockx, reverb, whatnot, airbnb, turo, shopify_collective, ubereats, doordash, ramp, brex, apple_cash, wise, chase, bank_of_america, wells_fargo, deel, remote, gusto, airwallex, revolut_business, mercury, coinbase, coinbase_exchange, coinbase_x402, coinbase_commerce, kraken, gemini, bitpay, strike, circle, skyfire, crossmint) and/or method (card_online, card_in_person, ach_debit, business_profile, ...). Use it to quote a provider's exact pricing or to check a number. If a platform is missing, say so to the owner; PaidRouter records the ask and adds it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
freshNoRe-read the provider's pricing page (or the live FX quote) now instead of using the last check. Slower. Up to 20 page reads per key per day. Use when the owner is about to act on the number.
methodNoe.g. card_online, ach_debit, business_profile
platformNostripe, square, paypal, venmo, cash_app, helcim, melio, payoneer, wise_business, shopify_payments, zelle, ebay, etsy, upwork, fiverr, amazon, quickbooks_payments, quickbooks_payments_desktop, freshbooks, wave, xero, gocardless, zoho_payments, bill_com, honeybook, bonsai, invoice2go, jobber, housecall_pro, toast, clover, godaddy_payments, wix_payments, squarespace_payments, lightspeed, sumup, paypal_pos, patreon, gumroad, kofi, buymeacoffee, substack, teachable, kajabi, podia, lemonsqueezy, paddle, fanfix, poshmark, mercari, depop, stockx, reverb, whatnot, airbnb, turo, shopify_collective, ubereats, doordash, ramp, brex, apple_cash, wise, chase, bank_of_america, wells_fargo, deel, remote, gusto, airwallex, revolut_business, mercury, coinbase, coinbase_exchange, coinbase_x402, coinbase_commerce, kraken, gemini, bitpay, strike, circle, skyfire, crossmint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / description
      Previous value: -"stripe, square, paypal, venmo, cash_app, helcim, melio, payoneer, wise_business, shopify_payments, zelle, ebay, etsy, upwork, fiverr, amazon"New value: +"stripe, square, paypal, venmo, cash_app, helcim, melio, payoneer, wise_business, shopify_payments, zelle, ebay, etsy, upwork, fiverr, amazon, quickbooks_payments, quickbooks_payments_desktop, freshbooks, wave, xero, gocardless, zoho_payments, bill_com, honeybook, bonsai, invoice2go, jobber, housecall_pro, toast, clover, godaddy_payments, wix_payments, squarespace_payments, lightspeed, sumup, paypal_pos, patreon, gumroad, kofi, buymeacoffee, substack, teachable, kajabi, podia, lemonsqueezy, paddle, fanfix, poshmark, mercari, depop, stockx, reverb, whatnot, airbnb, turo, shopify_collective, ubereats, doordash, ramp, brex, apple_cash, wise, chase, bank_of_america, wells_fargo, deel, remote, gusto, airwallex, revolut_business, mercury, coinbase, coinbase_exchange, coinbase_x402, coinbase_commerce, kraken, gemini, bitpay, strike, circle, skyfire, crossmint"
  2. Changed1 schema field changed
    • addedInput schema / properties / fresh
      Added value: +{
      +  "default": false,
      +  "description": "Re-read the provider's pricing page (or the live FX quote) now instead of using the last check. Slower. Up to 20 page reads per key per day. Use when the owner is about to act on the number.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description still discloses meaningful behavior: entries are sourced and dated ('the source URL and the date verified'), and missing-platform requests are recorded rather than silently failing. It omits the caching/freshness tradeoff and the 20-page-reads-per-day cap (both live only in the schema), leaving a gap for a no-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly three-quarters of the description is a ~75-item platform list repeated word-for-word in the schema's platform property. That bulk crowds out the genuinely useful sentences about sourcing, the method filter, and missing-platform handling.

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

Completeness4/5

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

There is no output schema, and the description compensates well by enumerating the returned fields (percent, fixed fee, caps, minimums, extras, source URL, date verified). Combined with the schema's documentation of `fresh` and the read budget, an agent has enough to call it correctly; only the response shape (flat list vs. grouped by method) remains unstated.

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 coverage is 100%, so the baseline is 3. The only value added beyond the schema is the 'platform and/or method' phrasing, clarifying the two filters can be combined — the platform enumeration itself is a verbatim duplicate of the schema's description.

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 the resource concretely (raw, sourced fee entries with percent, fixed fee, caps, minimums, extras, source URL, verification date) and positions itself as the underlying data behind other answers. It implicitly separates itself from explain_fees by being the 'raw' record rather than an explanation, though it never names that sibling outright.

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?

It gives explicit use cases — 'quote a provider's exact pricing or to check a number' — and an edge-case instruction for missing platforms ('say so to the owner; PaidRouter records the ask and adds it'). No named alternative or when-not-to-use clause, so it falls short of a 5.

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