Skip to main content
Glama

SwapHunt crypto market context

pm_fees

Read-onlyIdempotent

Free (does not count against the trial). Use when the user asks the fee for an order on Kalshi, Polymarket US or polymarket.com. Returns fee in USD and % of trade value, break-even exit after both fees, rates version. contracts = USD / price; polymarket needs category. Ex: platform=polymarket&price=0.4&contracts=250&category=Politics

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": "pm_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNoExit for break-even is the other sidebuy
tierNopolymarket-us: tier 1-4 or new
makerNoMaker order (Polymarket makers pay 0)
priceNoPrice in dollars, 0 < price < 1
categoryNoRequired if platform=polymarket
platformNokalshi
contractsNoContracts (shares) = USD amount / price
multiplierNokalshi: fee multiplier 1, 0.5 or 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds the important non-schema fact that the call is free and does not count against the trial, and, since there is no output schema, it spells out what is returned: fee in USD, percent of trade value, break-even exit after both fees, and rates version. It is silent on precision/rounding and error behavior.

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?

Short and front-loaded, opening with the free-of-quota caveat and the when-to-use sentence before the output and example details. The telegraphic fragments ('break-even exit after both fees, rates version') are dense but slightly hard to parse on first read.

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?

For an 8-parameter, zero-required tool with no output schema, the description covers the trigger, the return values, the platform-conditional requirement, the unit conversion, and a full example call. An agent can invoke it correctly without further inference.

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 88%, so the schema already documents most parameters; the description reinforces the key derived relation ('contracts = USD / price') and the category requirement for Polymarket. The worked example (platform=polymarket&price=0.4&contracts=250&category=Politics) adds concrete calling semantics that the schema alone does not show.

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: computes the fee for an order on Kalshi, Polymarket US or polymarket.com, and enumerates the outputs (fee in USD, % of trade value, break-even exit, rates version). This is clearly distinguishable from the sibling tools, which are unrelated data lookups.

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?

Gives an explicit trigger: 'Use when the user asks the fee for an order on Kalshi, Polymarket US or polymarket.com.' It also flags the platform-specific prerequisite ('polymarket needs category'). It does not name when-not-to-use or an alternative sibling, but none of the listed siblings appear to overlap.

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.