Skip to main content
Glama
yigitabi5444

Polymarket MCP Server

by yigitabi5444

get_sports_teams

Retrieve a list of teams for a specified sport on Polymarket to analyze prediction markets and monitor events.

Instructions

List teams for a given sport on Polymarket.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportNoSport code (e.g. 'nba', 'nfl', 'epl')

Implementation Reference

  • The tool definition and handler for "get_sports_teams" which invokes the GammaApi service.
    server.tool(
      "get_sports_teams",
      "List teams for a given sport on Polymarket.",
      {
        sport: z.string().optional().describe("Sport code (e.g. 'nba', 'nfl', 'epl')"),
      },
      async (args) => {
        try {
          const data = await gamma.getSportsTeams(args.sport);
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error: ${(error as Error).message}` }],
            isError: true,
          };
        }
      },
    );
  • The actual implementation of the "getSportsTeams" logic that fetches data from the API client.
    async getSportsTeams(sport?: string): Promise<GammaSportsTeam[]> {
      const query: Record<string, string | undefined> = {};
      if (sport) query.sport = sport;
      return this.client.gamma<GammaSportsTeam[]>("/sports/teams", query, CACHE_TTLS.sports);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't cover aspects like rate limits, authentication needs, pagination, or error handling. This is a significant gap for a tool with no annotation coverage.

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?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence earns its place by specifying the action, resource, and context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., list format, fields), error cases, or behavioral traits. For a tool with no structured support, this leaves significant gaps for an AI agent to use it effectively.

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?

The schema description coverage is 100%, with the single parameter 'sport' documented as 'Sport code (e.g. 'nba', 'nfl', 'epl')'. The description adds no additional meaning beyond this, such as explaining what 'Polymarket' is or providing more context on sport codes. Baseline 3 is appropriate 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?

The description clearly states the action ('List teams') and the resource ('for a given sport on Polymarket'), which provides a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_sports' or 'get_events', which might be related but serve different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for usage, or exclusions, leaving the agent to infer based on the tool name and parameters alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yigitabi5444/yigit_polymarket_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server