Skip to main content
Glama

Marginrule pricing agent

Fees and take-home at a price

fees_breakdown
Read-onlyIdempotent

Fees a platform takes from one sale at a given price, split into platform, listing and card processor parts, plus net after fees and, with an optional cost, profit and margin (a fraction). buyer_tax_rate is a FRACTION (0.07 = 7%). US sellers only. Read-only.

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>",
      "price": "<price>"
    },
    "name": "fees_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
costNoOptional cost per item in USD, so the answer includes profit and margin. Default 0.
priceYesSale price in USD before buyer sales tax, in whole cents, at least 0.01, e.g. 17.
regionNoBuyer location relative to a US seller. "us" (default) = domestic. "international" is only modelled with processor "paypal" (adds PayPal's 1.50% international fee, so 4.99% + $0.49); other combinations return an error rather than a guess.
platformYesPlatform and plan id from list_platforms, e.g. "etsy", "payhip-free", "gumroad-direct", "ko-fi-shop".
processorNoCard processor for platforms where the seller adds their own (Payhip plans, Ko-fi Shop). "stripe" = 2.9% + $0.30 (default). "paypal" = PayPal Checkout or Guest Checkout, 3.49% + $0.49. Ignored, with a note, for platforms that charge their own processing (Etsy, Shopify, Gumroad, Notion, Square).
buyer_tax_rateNoBuyer's sales tax as a FRACTION, e.g. 0.07 for 7%. Default 0. Tax is never profit; it only raises card processing on platforms that charge processing on the tax-inclusive total (see each platform's tax_base).
processor_rateNoAdvanced override: your own card processor percentage as a FRACTION (0.029 = 2.9%). Only for platforms where the seller adds their own processor. Replaces the preset's rate.
processor_fixed_usdNoAdvanced override: your card processor's fixed fee per sale in USD, e.g. 0.30. Replaces the preset's fixed fee.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds value beyond that by disclosing the result composition (fee components, net, optional profit and margin expressed as a fraction) and a jurisdictional limitation (US sellers only). It does not state rounding behavior or the exact response shape, which matters somewhat given no output schema.

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 content is packed into a short block with the core computation and the returned components front-loaded, followed by the fraction convention and scope limits. The 'buyer_tax_rate is a FRACTION' clause is duplicative of the schema and slightly interrupts the flow, but no sentence is wasted overall.

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?

With eight parameters, an input schema that documents everything, and no output schema, the description responsibly enumerates what comes back (component fees, net, profit, margin) and flags the US-only scope. Minor gaps remain around output structure and rounding, but nothing that would cause a wrong invocation.

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% and the schema already defines every parameter in detail, including the enum values, processor override behavior, and the fraction convention. The description's note that buyer_tax_rate is a FRACTION and that margin is a fraction restates what the schema says, so it adds no meaning beyond the structured field. 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?

The description names a specific computation: fees taken from one sale at a given price, decomposed into platform, listing and card processor parts, plus net and optional profit/margin. That is far more than a restatement of the name, and an agent can tell it computes a forward fee breakdown rather than a price search. It stops short of differentiating itself from price_for_margin, even though both can return a margin when cost is supplied.

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 implied rather than stated: give a price to get fees/net, add cost to also get profit and margin. The 'US sellers only' scope note is a useful applicability constraint, but there is no explicit when-to-use-this vs when-to-use-price_for_margin guidance despite the obvious overlap on margin output.

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