Skip to main content
Glama

Pulltrader

by app.pulltrader
OverviewDiscussionsAdmin

Compare trading-card seller proceeds across selling methods

compare_selling_costs

Compare estimated fees and the net amount a trading-card seller keeps when selling the SAME card across eBay (estimated), Pulltrader selling methods (marketplace, Fulfilled by Pulltrader, branded storefront, and in-person POS), and other marketplaces (TCGplayer, Mana Pool, Misprint, Fanatics Collect, Goldin — estimated fixed-price/Buy Now seller fees). Use this when a seller asks what they would keep/net/take-home on a sale, how fees compare between platforms, or which method leaves them with more money. Calculations are deterministic and use dated fee schedules. Competitor marketplaces are off by default; include them via the methods field. Only fixed-price seller fees are modeled — auction formats (hammer price, buyer's premium, negotiated consignment) are not. Do NOT use this to look up a card's market value or recent sales (this tool does not price cards), and do NOT use it for non-trading-card categories. Present competitor and eBay figures as estimates, never as guaranteed proceeds, and never claim one platform is universally cheapest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodsNoWhich selling methods to compare. Defaults to eBay, Pulltrader marketplace, and Pulltrader storefront. Other supported methods (off by default): pulltrader_fbp, pulltrader_pos, and estimated competitor marketplaces tcgplayer, manapool, misprint, fanatics_collect, goldin.
currencyNoISO currency code. Only USD is supported.USD
quantityNoNumber of identical items in one order. Per-order fixed fees are applied once.
sale_priceYesThe per-item sale price (the card's listed/sold price), in the given currency.
seller_planNoPulltrader seller plan. Sets the payout floor (free/operations=91%, business/managed=95%); a seller level earned on revenue can be higher.free
seller_levelNoThe seller's actual level (1-5), if known. Level is set from plan AND sales volume, so levels 2 and 4 exist only by earning them and cannot be inferred from a plan. Overrides the plan's rate: 1=91%, 2=92%, 3=93%, 4=94%, 5=95%.
item_categoryNoItem category. Only trading_cards is supported.trading_cards
shipping_amountNoShipping amount charged to the buyer. Affects eBay's fee base. See assumptions for how each method treats shipping.
acquisition_costNoOptional. What the seller paid for the card; used to estimate net profit per method.
seller_covers_feesNoIf true, the seller absorbs the Pulltrader platform fee (3.25% + $0.40). If false (default), the buyer pays it at checkout. The platform fee is always charged on Pulltrader card sales regardless.
ebay_store_subscriptionNoIf true, estimate eBay fees using the eBay Basic-or-higher Store subscriber rate (12.35% up to $2,500/item) instead of the individual rate (13.25% up to $7,500/item).
ebay_fee_percent_overrideNoOptional. Override the estimated eBay final value fee percentage (e.g. for a seller with an eBay Store subscription).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ebay_store_subscription / description
      Previous value: -"If true, estimate eBay fees using the eBay Store subscriber rate (12.35% up to $2,500/item) instead of the individual rate (13.25% up to $7,500/item)."New value: +"If true, estimate eBay fees using the eBay Basic-or-higher Store subscriber rate (12.35% up to $2,500/item) instead of the individual rate (13.25% up to $7,500/item)."
  2. Changed3 schema fields changed
    • addedInput schema / properties / seller_level
      Added value: +{
+  "description": "The seller's actual level (1-5), if known. Level is set from plan AND sales volume, so levels 2 and 4 exist only by earning them and cannot be inferred from a plan. Overrides the plan's rate: 1=91%, 2=92%, 3=93%, 4=94%, 5=95%.",
+  "enum": [
+    1,
+    2,
+    3,
+    4,
+    5
+  ],
+  "type": "integer"
+}
    • changedInput schema / properties / seller_plan / description
      Previous value: -"Pulltrader seller plan. Determines the marketplace payout tier (free=91%, starter=93%, pro=94%, shop=95%)."New value: +"Pulltrader seller plan. Sets the payout floor (free/operations=91%, business/managed=95%); a seller level earned on revenue can be higher."
    • changedInput schema / properties / seller_plan / enum
      Previous value: -[
-  "free",
-  "starter",
-  "pro",
-  "shop"
-]New value: +[
+  "free",
+  "operations",
+  "business",
+  "managed"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / methods / description
      Previous value: -"Which selling methods to compare. Defaults to eBay, Pulltrader marketplace, and Pulltrader storefront."New value: +"Which selling methods to compare. Defaults to eBay, Pulltrader marketplace, and Pulltrader storefront. Other supported methods (off by default): pulltrader_fbp, pulltrader_pos, and estimated competitor marketplaces tcgplayer, manapool, misprint, fanatics_collect, goldin."
    • changedInput schema / properties / methods / items / enum
      Previous value: -[
-  "ebay",
-  "pulltrader_marketplace",
-  "pulltrader_fbp",
-  "pulltrader_storefront",
-  "pulltrader_pos"
-]New value: +[
+  "ebay",
+  "pulltrader_marketplace",
+  "pulltrader_fbp",
+  "pulltrader_storefront",
+  "pulltrader_pos",
+  "tcgplayer",
+  "manapool",
+  "misprint",
+  "fanatics_collect",
+  "goldin"
+]
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations, so the description carries the burden and does well: deterministic calculations, dated fee schedules, competitor marketplaces off by default, only fixed-price fees (auctions excluded), and a presentation caveat (estimates never guarantees). It could say more about response shape, but for a read/compute tool this is strong.

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?

Front-loads what is compared, then when-to-use, then constraints. Dense but every clause is substantive; the final presentation rules are slightly discursive but justified for an estimate-producing tool.

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?

For a 12-parameter compute tool with no output schema or annotations, the description covers scope, defaults, estimation caveats, and exclusions. Missing only explicit mention of what the response contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining the default method set and the rationale for off-by-default competitors, and it clarifies that competitor figures are estimated fixed-price seller fees.

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: compare fees and net proceeds across named selling methods. It distinguishes itself from siblings by explicitly saying it does NOT price cards (get_card_price_history, search_card_sales) and hands off to nothing else.

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?

Gives concrete triggers ('what they would keep/net/take-home', 'how fees compare', 'which method leaves them with more money') and explicit exclusions (not for card value, not for non-trading-card categories). The default-vs-opt-in behavior of competitor methods is stated.

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

All Pulltrader toolsInspect
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