Skip to main content
Glama

taker_fee

Compute the taker fee for Polymarket markets based on price, shares, and optional category. The fee varies by category such as crypto or sports.

Instructions

Official Polymarket taker fee in $ (fee = rate * p * (1-p) * shares). Categories and rates: crypto 0.07, sports 0.03, finance/politics/mentions/ tech 0.04, economics/culture/weather 0.05, geopolitics 0. Makers pay 0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceYes
sharesYes
categoryNocrypto

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Describes the calculation formula and lists rates, which is transparent about its behavior. No annotations exist, so description carries full burden; it adequately discloses the fee computation but does not mention if it is read-only or has side effects.

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?

Concise single sentence plus a list of categories. The line break in the list is minor, but overall efficient with no unnecessary words.

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?

Given the simple calculation and existence of output schema, the description covers the essential formula and category rates. But lacks explanation of what the output represents and any prerequisites or edge cases.

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?

With 0% schema coverage, description partially compensates: the formula explains price and shares as inputs (p and shares), and category is linked to rates. However, it does not specify units, ranges, or meaning for price and shares beyond the formula.

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?

Clearly states it computes the official Polymarket taker fee, provides the formula and lists categories with rates. Distinguishes from sibling tools which are about accounts, books, and markets.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool or when to avoid it. Only lists categories and rates without indicating alternatives or conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/crp4222/pmq'

If you have feedback or need assistance with the MCP directory API, please join our Discord server