Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket perps tickers

polymarket_perps_tickers_list
Read-onlyIdempotent

Lists Polymarket perpetual futures prices, open interest, and funding, optionally filtered by instrumentId, to help monitor market conditions.

Instructions

List Polymarket perps prices, open interest and funding. Optional inputs: instrumentId. Returns a list.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_perps_tickers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
instrumentIdNoOnly this instrument. Default: all.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

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, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the payload content (prices, open interest, funding) and that the result is a list, but says nothing about pagination, result size, or whether funding is a rate or an absolute value.

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?

Three short sentences with the core payload description front-loaded and no filler. It is terse to the point of omitting useful detail, 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?

With no output schema, the description carries the burden of describing return values, and 'Returns a list' is only marginally informative. For a read-only list tool with full schema coverage and rich annotations this is adequate, but the shape of a ticker record and any result limits are left unexplained.

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 100%, so all four parameters are documented in the schema, including instrumentId's 'Only this instrument. Default: all.' The description repeats the optionality of instrumentId without adding syntax or filtering semantics beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (list) and resource (Polymarket perps tickers) and names the payload fields: prices, open interest, funding. It does not explicitly differentiate from close siblings like polymarket_perps_instruments_list or polymarket_perps_klines_list, but the field enumeration gives a reasonable idea of the distinction.

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 or when-not-to-use guidance. An agent must infer from the field list that this is a per-instrument snapshot rather than an instrument catalog or a time series, and nothing routes it to alternatives such as the instruments or klines tools.

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

Deploy Server

Other Tools