mcp-server-polymarket

Overview Schema Source Related Servers Discussions Admin

Get Perps exchange info

get_perps_exchange_info

Read-onlyIdempotent

Retrieve perpetuals exchange configuration: chain and settlement contract, cancel-only status, collateral assets, withdrawal fees, maker/taker fee tiers, and account rate limits.

Instructions

The Perps exchange: chain and settlement contract, whether it is cancel-only, collateral assets and withdrawal fees, the maker/taker fee tiers, and account rate-limit tiers.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`errors`	No
`exchange`	No
`limit_tiers`	No
`fee_schedule`	No
`collateral_assets`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds useful context about what the payload contains (static config-like data: cancel-only status, fees, rate-limit tiers) but says nothing about freshness, caching, or whether fees are current vs. scheduled.

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?

A single sentence that front-loads the resource and then lists contents, with no filler. It reads as a fragment rather than a sentence, but it is compact and scannable.

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?

With no parameters and an output schema present, the description needn't document return values, and annotations cover safety. The only real gap is the missing differentiation from get_perps_exchange_stats, which is a guidance issue rather than a completeness one.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. Schema coverage is 100% and the empty object schema leaves no ambiguity.

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

Purpose3/5

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

The description is a noun phrase enumerating the contents of the Perps exchange record (chain, settlement contract, cancel-only flag, collateral assets, withdrawal fees, fee tiers, rate limits), which conveys what data comes back. However, it never states an action verb ('Retrieves...') and does not distinguish this from the sibling get_perps_exchange_stats, which an agent could easily confuse it with.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_perps_exchange_stats. The agent must infer the calling context entirely from the field listing.

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

Deploy Server