Skip to main content
Glama

Fliprofit reseller fee calculator

Dated marketplace fee changes

get_fee_changes
Read-onlyIdempotent

Machine-readable log of real, dated US marketplace fee changes (rate changes, new fees, caps, promotions, ending discounts), each with the platform's own source URL and the date Fliprofit last verified it. Filter by platform, by effective date, or to upcoming changes only.

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_fee_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoOnly changes effective on or after this date (YYYY-MM-DD).
platformNoOnly this platform.
upcomingNoOnly changes not yet in effect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "ebay",
      -  "poshmark",
      -  "mercari",
      -  "whatnot",
      -  "depop",
      -  "etsy",
      -  "facebook",
      -  "amazon",
      -  "grailed",
      -  "reverb",
      -  "tcgplayer",
      -  "tiktok"
      -]New value: +[
      +  "ebay",
      +  "poshmark",
      +  "mercari",
      +  "whatnot",
      +  "depop",
      +  "etsy",
      +  "facebook",
      +  "amazon",
      +  "grailed",
      +  "reverb",
      +  "tcgplayer",
      +  "tiktok",
      +  "vinted"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

It provides significant behavioral context beyond the annotations, detailing that the log includes the platform's 'own source URL' and the 'date Fliprofit last verified it.' This adds critical data provenance and quality context that annotations cannot cover.

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?

The definition is highly efficient and structured. It front-loads the tool's core function ('Machine-readable log') and provides a clear list of filtering capabilities without unnecessary filler.

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?

The definition is extremely complete for a read-only log retrieval tool. It covers what the data is (fees, changes), how it's verified (Fliprofit date/URL), and the three key ways it can be filtered, leaving no critical ambiguity for the agent.

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?

Given that schema description coverage is 100%, the baseline score of 3 is appropriate. The description reinforces the filtering intent ('Filter by platform, by effective date, or to upcoming changes only') but does not add any meaning or nuance that is absent from the schema's definitions.

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 clearly defines the resource as a 'Machine-readable log of real, dated US marketplace fee changes.' It specifies the exact nature of the data (rate changes, new fees, caps) and its scope, distinguishing it from calculation or comparison tools.

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 defines the tool's primary function—retrieving data via filtering—by mentioning the ability to filter by platform, effective date, or upcoming changes. While it doesn't explicitly forbid use in comparison scenarios, it strongly defines its intended retrieval role.

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