Flip Fee Calculator

list_marketplaces

Read-onlyIdempotent

Use FIRST when you need to know which marketplaces are supported, their ids, or the fee assumptions behind any result: seller fee rates and fixed fees, payment processing, payout methods and fees, buy-side premiums/extraction fees, vault intake, shipping handling, plus the source URL, date checked and verification status of each figure. Figures without a recorded source are marked unverified. Read-only, no inputs required.

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": "list_marketplaces"
  }
}

Input Schema

Name	Required	Description	Default
`marketplace`	No	Optional: return just this marketplace

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses provenance behavior: source URLs, dates checked, verification status, and explicit marking of figures without recorded sources as unverified. These details help the agent interpret the reliability of returned fee data.

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 usage instruction is front-loaded, and the provenance and verification sentences are compact and useful. The opening sentence is somewhat dense because of its exhaustive fee-category enumeration, but there is little genuinely irrelevant wording.

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?

For a simple read-only tool with one optional, fully documented parameter, the description covers invocation timing, returned content, and data-verification behavior. It also compensates for the absent output schema by enumerating the principal result fields without needing to document return syntax.

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%, including the optional marketplace filter and its enum, so the baseline applies. 'No inputs required' confirms that a zero-argument call is valid but adds little beyond the schema's lack of required parameters.

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?

The description identifies the supported-marketplace listing, marketplace IDs, and detailed fee-assumption metadata as the tool's resources. Its emphasis on assumptions behind any result distinguishes this metadata lookup from the calculation and evaluation siblings.

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

Usage Guidelines5/5

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

The front-loaded 'Use FIRST' supplies explicit sequencing, followed by concrete triggers: checking supported marketplaces, obtaining IDs, or inspecting fee assumptions. This gives the agent clear guidance on when to call it before relying on downstream results.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Flip Fee Calculator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?