Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket teams

polymarket_teams_list
Read-onlyIdempotent

Lists sports teams and fighters that have Polymarket markets, with optional filters for league or name and cursor-based pagination.

Instructions

List the sports teams and fighters Polymarket has markets for. Optional inputs: league, name, limit and cursor. Returns a list (use cursor when paginated).

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_teams_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOnly teams with this name.
limitNoItems per page, 1–100. Default: 100.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other filters the same.
leagueNoOnly teams in this league, by code such as `nfl`.
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

A3.6/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 only the pagination behaviour ('use cursor when paginated'), and says nothing about server-side limits, ordering, or the required analytics bookkeeping parameters that the schema enforces.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, the purpose front-loaded and the pagination note trailing. Nothing is redundant and every clause carries information.

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?

For a read-only list tool with 100% schema coverage and no output schema, the description covers purpose and pagination, which is most of what an agent needs. It is slightly thin on what a returned team object looks like and on whether filters combine, but no critical calling information is missing.

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 every parameter including league, name, limit and cursor is already documented in the schema. The description merely restates the optional input names and adds no format or semantics beyond what is structured. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('List the sports teams and fighters Polymarket has markets for'), which is concrete and scoped. It does not explicitly distinguish itself from the closest sibling, polymarket_sports_list, so an agent must infer that one returns sports and the other returns teams within those sports.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description names the optional filters and gives a cursor usage hint ('use cursor when paginated'), which implies how to page. It offers no when-to-use guidance or exclusions, and never points at an alternative such as polymarket_sports_list for league-level browsing.

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