Skip to main content
Glama

Fliprofit reseller fee calculator

Compare all platforms for one sale

compare_platforms
Read-onlyIdempotent

Ranks all 13 supported US resale platforms by profit for the same sale (each platform's default options). Returns fees, payout, profit and margin per platform, with a link to each fliprofit.com calculator and the side-by-side compare tool.

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

Input Schema

NameRequiredDescriptionDefault
priceYesSale price in USD (required).
taxRateNoBuyer sales tax percent, e.g. 8 (default 0). Used where the platform charges fees on tax.
itemCostNoWhat you paid for the item, USD (default 0).
shipCostNoYour label/postage cost, USD (default 0).
otherCostNoPackaging, promotion and other costs, USD (default 0).
shipChargedNoShipping the buyer paid you, USD (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 real behavioral context beyond that: it discloses the result payload (fees, payout, profit, margin per platform) and that each row includes a calculator link plus a compare-tool link, so the agent knows output shape without an 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.

Conciseness5/5

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

Two sentences, front-loaded with the action and scope, followed by the return contents. No filler, no restatement of the title or annotations.

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?

There is no output schema, so the description carries the burden of describing return values — and it does, listing the per-platform metrics and embedded links. Combined with 100% schema coverage on inputs and full annotation coverage, an agent has everything needed to call and interpret this tool correctly.

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 all six parameters (price, taxRate, itemCost, shipCost, otherCost, shipCharged) are documented in the schema itself and the description does not need to repeat them. The phrase 'each platform's default options' adds a small but genuine constraint — per-platform fee settings cannot be overridden here — but no parameter-level meaning beyond the schema is provided.

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?

States a specific verb and resource — 'Ranks all 13 supported US resale platforms by profit' — plus the scope qualifier 'for the same sale (each platform's default options)'. This clearly separates it from calculate_fees (single calculation) and get_fee_changes (historical/rate data).

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: an agent can infer it is the cross-platform comparison entry point, but the description never states when to prefer it over calculate_fees, nor any exclusion such as 'for a single platform, use calculate_fees'. The 'each platform's default options' note hints at the boundary between this tool and per-platform custom calculations but does not say so explicitly.

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