Skip to main content
Glama

Explain fees

explain_fees

When the owner asks why a provider took a certain amount ('why did PayPal take $35 from my $1,000?'). Give the platform, the method and the amount; returns a plain-words explanation: the fee, the formula, the effective percent, extras that can apply, and the source.

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": {
      "platform": "<platform>",
      "method": "<method>"
    },
    "name": "explain_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.
amountNo
methodYese.g. paypal_checkout, card_online, ach_debit
platformYesstripe, 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.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does well on outputs (plain-words explanation, formula, effective percent, caveats, source), but it's silent on the staleness/caching behavior — that it uses the last pricing check by default and only re-reads when 'fresh' is set — and on the rate limit that governs that. That is the most consequential behavioral trait of this tool and it is only in the schema.

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?

Three compact clauses: a concrete trigger, an input instruction, an output promise. Front-loaded with the scenario an agent is most likely to match against, and the enumerated return contents earn their space given there is no output schema.

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?

Because there is no output schema, the description must convey return values, and it does so adequately (fee, formula, effective percent, extras, source). The one gap is that it does not mention the default-to-cached-pricing behavior, which affects whether an agent should set fresh before the owner acts on the number.

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 75%, so the schema already documents platform, method, and fresh in detail. The description reinforces which inputs to supply ('the platform, the method and the amount') and that amount is optional context, but adds nothing about the fresh flag or the format of method values beyond what the schema states. Baseline 3 applies.

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?

States a specific verb+resource (explain fees) and describes the output shape (fee, formula, effective percent, extras, source), which distinguishes it from a raw-number tool like get_fees. It never names a sibling, so the differentiation is implicit rather than explicit.

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 opening parenthetical gives a concrete triggering situation ('why did PayPal take $35 from my $1,000?'), which is a clear use signal. However, it offers no exclusions or pointers to alternatives such as get_fees, my_effective_rate, or compare_send_money, so an agent must infer when this tool is the wrong choice.

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