Skip to main content
Glama

Polymarket platform fee

pm_platform_fee
Read-only

Exact taker fee for a Polymarket trade: shares x feeRate x p(1-p). Makers pay nothing on the global exchange. Also returns maker rebate, optional builder fee and the fee as a percentage of notional.

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": {
      "category": "<category>",
      "shares": "<shares>",
      "price": "<price>"
    },
    "name": "pm_platform_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
roleNo
sideNo
priceYes
sharesYes
categoryYes
builder_bpsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already covering the safety profile, the description adds real behavioral value: the exact fee formula, the maker-pays-zero rule on the global exchange, and the extra outputs (maker rebate, builder fee, percentage of notional). It does not explain what changes between the 'global' and 'us' kinds, which is the one behavioral branch left dark.

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?

Three short sentences, front-loaded with the formula and the primary output, followed by the maker exception and the secondary return values. No filler and no repetition of what the name already says.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only calculator with no output schema, the description does a reasonable job naming the returned fields and giving the formula. It falls short on the global-vs-us fee regime and the role of category in determining the rate, which are material to calling it 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 description coverage is 0%, so the description has to carry the load, and it does partially: shares, price, and builder_bps map onto the formula, and role is covered by the maker/taker fee distinction. It says nothing about 'kind' (global vs us), 'side' (buy/sell), or how the required 'category' drives feeRate, leaving three parameters unexplained in both schema and prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Exact taker fee for a Polymarket trade') and even supplies the pricing formula, which makes the tool's role unmistakable. It never names a sibling, but the fee-computation purpose is distinct enough from market briefs, fill simulation, and reward eligibility that confusion is unlikely.

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?

There is useful conditional guidance embedded in 'Makers pay nothing on the global exchange', which tells an agent when the result is zero. However, there is no explicit when-to-use versus when-to-use-an-alternative statement, and nothing tells the agent how to choose between this and the fee-adjacent siblings such as pm_order_book_fill.

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