Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

pm_fees

Read-only

Calculate order fees for Kalshi and Polymarket, including fee USD, percentage, and break-even exit price, to plan trades before filling.

Instructions

Free, runs locally (no API call, no payment). Use when the user asks the fee for an order on Kalshi, Polymarket US or polymarket.com. Returns fee_usd, fee %, break-even exit, rates as_of. contracts = USD / price; polymarket needs category; at = fill time (default now). Ex: platform=polymarket, price=0.4, contracts=250, category=Politics

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": {
      "platform": "<platform>",
      "price": "<price>",
      "contracts": "<contracts>"
    },
    "name": "pm_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
sideNotaker
tierNo
priceYes
categoryNo
platformYes
contractsYes
directionNobuy
multiplierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly and non-destructive, so the safety profile is covered; the description adds genuinely new context by disclosing it is free, runs locally, makes no API call and requires no payment. It also enumerates the response fields (fee_usd, fee %, break-even exit, rates_as_of), which matters since there is no output schema. It does not discuss rate-limit or as-of staleness beyond naming the field.

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-loaded with the highest-value fact (free, local) and then the trigger, return shape, and a worked example in a compact telegraphic style with no filler. The telegraphic compression occasionally hurts clarity ('contracts = USD / price' is terse), but nothing is wasted.

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 9-parameter tool with 0% schema coverage and no output schema, the description covers the return shape and the core required inputs plus one example, which is meaningful compensation. The unexplained side/tier/direction/multiplier parameters and the ambiguous contracts formula leave real gaps an agent could get wrong.

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 coverage is 0% across 9 parameters, so the description must compensate. It explains the units linkage ('contracts = USD / price'), that polymarket requires category, and that at is fill time defaulting to now, and the example demonstrates platform/price/contracts/category. However side (taker/maker), tier, direction and multiplier are never explained, leaving roughly half the parameters without 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?

States a specific verb and resource ('the fee for an order') plus the covered venues (Kalshi, Polymarket US, polymarket.com) and the returned fields. None of the sibling tools (funding rates, fear & greed, volatility) overlap, so an agent can route this unambiguously.

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.' That is a clear when-to-use condition. It stops short of stating exclusions or naming an alternative for adjacent questions (e.g. general pricing vs. fee), but no relevant sibling exists to route to.

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