Skip to main content
Glama
Sign In
Odds-API MCP Server

Odds-API MCP Server

Official
by odds-api-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List participants

get_participants
Read-onlyIdempotent

Retrieve teams or players for a sport, optionally filtered by name, and return IDs for use as participantId in event lookups.

Instructions

Teams or players for a sport, optionally filtered by name. Returns id and name (esports also game and shortCode). Use the id as participantId in get_events.

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": {
      "sport": "<sport>"
    },
    "name": "get_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportYesSport slug from get_sports (e.g. 'football', 'basketball', 'tennis')
fieldsNoOptional comma-separated top-level fields to keep on each item (e.g. 'id,home,away,date,status'). Trims large responses.
searchNoFilter by team/participant name
maxResultsNoOptional cap on the number of items returned to you (applied after the API call).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.8.3
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Optional comma-separated top-level fields to keep on each item (e.g. 'id,home,away,date,status'). Trims large responses.",
+  "type": "string"
+}
    • addedInput schema / properties / maxResults
      Added value: +{
+  "description": "Optional cap on the number of items returned to you (applied after the API call).",
+  "type": "number"
+}
    • changedInput schema / properties / search / description
      Previous value: -"Search term to filter by team/participant name"New value: +"Filter by team/participant name"
    • changedInput schema / properties / sport / description
      Previous value: -"Sport slug (e.g., 'football')"New value: +"Sport slug from get_sports (e.g. 'football', 'basketball', 'tennis')"
  2. First observedv1.5.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, so the description only needs to add context. It does so meaningfully by disclosing the return payload shape (id and name, plus game and shortCode for esports), which matters because no output schema exists.

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?

Three compact sentences, front-loaded with the resource and scope, then the return shape, then the linkage to get_events. Every sentence carries distinct information with no waste.

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 output schema, the description compensates by describing the returned fields and their use in a follow-up call. For a simple list tool with full schema coverage and clear annotations, this covers nearly everything an agent needs, with only pagination behavior left 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 schema already documents all four parameters, and the description only restates the name filter. Baseline 3 applies since the description adds little semantic meaning beyond the structured fields.

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 gives a concrete verb and resource ('Teams or players for a sport') plus its filtering capability, so the agent knows exactly what comes back. It does not explicitly contrast with the singular get_participant sibling, so differentiation is only implied by the plural form.

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 closing sentence 'Use the id as participantId in get_events' gives real downstream workflow guidance, which is stronger than typical. However, there is no guidance on when to prefer this over get_participant or search_events, and no exclusions or prerequisites are stated.

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