Skip to main content
Glama

Pulltrader Seller Economics

by app.pulltrader

Explain how a supported selling method works and what fees apply

explain_selling_method

Return a plain, structured explanation of one or more supported trading-card selling methods: who owns the listing, who fulfills, where it sells, the fee components that apply, and important caveats. Covers eBay (estimated), Pulltrader marketplace, Fulfilled by Pulltrader, branded storefront, in-person POS, and estimated competitor marketplaces (TCGplayer, Mana Pool, Misprint, Fanatics Collect, Goldin). Use this when a seller asks how a method works, what fees a platform charges, or how Pulltrader selling options differ. Do NOT use this to compute a specific payout (use compare_selling_costs) or the price needed for a target net (use calculate_required_sale_price), and do NOT use it to price cards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodsNoWhich selling methods to explain. Defaults to all supported methods: ebay, pulltrader_marketplace, pulltrader_fbp, pulltrader_storefront, pulltrader_pos, tcgplayer, manapool, misprint, fanatics_collect, goldin.

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explains the tool returns a 'plain, structured explanation' and lists the aspects covered (who owns, fulfills, fees, caveats), making it clear this is a read-only informational operation. However, it does not explicitly state that no data is modified or that it does not call external APIs, which would improve transparency. The description is still strong overall.

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 description is concise yet informative: two paragraphs with no wasted sentences. It front-loads the purpose and includes necessary details about what is explained and what is excluded. Every sentence serves a purpose, making it easy to parse quickly.

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?

Without an output schema, the description must explain the return value. It states the explanation is 'plain, structured' and covers specific aspects (ownership, fulfillment, fees, caveats), which is fairly complete. However, it does not describe the exact structure (e.g., whether it's a list or paragraphs) or mention any edge cases, leaving a minor gap.

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% with a clear description of the 'methods' parameter. The tool description adds value by naming each method and indicating which are 'estimated' (eBay, competitor marketplaces), providing context beyond the schema's enum list. This extra detail helps the agent understand the parameter's meaning.

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 states the tool returns a 'plain, structured explanation' of selling methods, specifying what aspects it covers (ownership, fulfillment, fees, caveats) and lists all supported methods. It distinguishes itself by explicitly stating what the tool is not for, contrasting with siblings like 'compare_selling_costs' and 'calculate_required_sale_price'.

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 description provides explicit guidance on when to use the tool ('when a seller asks how a method works, what fees a platform charges, or how Pulltrader selling options differ') and exactly when not to use it, including alternative tools for specific tasks. This clear differentiation helps an agent decide correctly.

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

All Pulltrader Seller Economics toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct operation: calculating prices, comparing costs, explaining methods, identifying cards, searching sales, summarizing markets, and fetching price history. No functional overlap exists between any pair.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., calculate_required_sale_price, compare_selling_costs, explain_selling_method) with no mixed conventions or abbreviations.

Tool Count5/5

With 7 tools covering pricing, fee comparison, method explanations, card identification, sales search, market summary, and price history, the set is well-scoped for a seller economics domain—neither too sparse nor bloated.

Completeness5/5

The tool surface comprehensively covers the seller economics lifecycle: card identification, market data (recent sales, price history, summary), fee/cost comparison, target-pricing calculation, and method explanation. No obvious dead ends for the stated purpose.

Resources