Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket sports

polymarket_sports_list
Read-onlyIdempotent

List sports and leagues Polymarket offers, optionally filtered by league code, to find available sports markets before fetching odds or details.

Instructions

List the sports and leagues Polymarket lists markets for. Optional inputs: sport. 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_sports_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportNoOnly this league, by code such as `nfl` or `epl`.
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.
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 by structured data. The description adds almost nothing beyond 'Returns a list', omitting whether an unknown sport code yields an empty list or an error, and giving no hint about the shape of the returned entries.

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?

Two sentences, front-loaded with the purpose statement with no filler. The trailing 'Returns a list.' is near-redundant given the readOnly list annotations and a named 'list' tool, so it is the one sentence that does not fully earn its place.

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?

This is a simple, annotated, read-only list tool with no output schema, so the bar is modest, but the description could have stated that returned league codes feed the `sport` filter on other tools. As written it is adequate but leaves the discovery-to-use relationship unstated.

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 description coverage is 100%, so the baseline is 3; the schema fully documents sport, context, llm_model, and conversation_id. The description only echoes the `sport` parameter as an optional input and says nothing about the two required parameters, which is slightly incomplete but harmless because the schema is authoritative.

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?

The description names a specific verb and resource: list the sports and leagues Polymarket covers. That is distinct from sibling tools like polymarket_teams_list or polymarket_tags_list, though it never explicitly contrasts itself with them, leaving the differentiation to the reader's inference from the name.

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 at all: no statement of when an agent should call this versus polymarket_teams_list, polymarket_events_list, or polymarket_markets_list, and no note that this is the discovery step for league codes. The only usage signal is the implicit 'optional sport filter'.

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