Skip to main content
Glama
Sign In
getodds-mcp

getodds-mcp

Official
by getoddsapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Search events by team name

search_events
Read-only

Find retained sports events by case-insensitive team name and return source-specific event IDs for odds and line-history lookups.

Instructions

Literal, case-insensitive team-name search over retained events. Returns source-specific event ids for get_odds and get_line_history.

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": {
      "q": "<q>"
    },
    "name": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
limitNo
sportNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond them: matching is literal and case-insensitive (not fuzzy or ranked), and only 'retained' events are searchable, warning that older events may be absent. It does not discuss empty results or how limit/pagination behaves.

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, front-loaded with matching semantics and scope, then the return value and downstream use. No wasted words or filler.

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 search with no output schema, the description covers return type ('event ids'), matching behavior, retention scope, and the follow-up tools. The main remaining gap is result-volume behavior (limit defaults, no-results cases), which is partially implied by the schema bounds.

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 0%, so the description carries the burden; it clarifies that 'q' is a team name matched literally and case-insensitively, which is genuine added meaning. However, neither 'limit' nor 'sport' is mentioned, leaving two of three parameters entirely to inference from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (team-name search) plus the matching semantics ('literal, case-insensitive') and the scope ('retained events'). It also states what the tool returns (source-specific event ids) and which siblings consume them, which cleanly separates it from get_odds/get_line_history.

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

Usage Guidelines4/5

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

The sentence 'Returns source-specific event ids for get_odds and get_line_history' effectively tells the agent this is the discovery/entry step before odds lookups. There is no explicit when-not guidance (e.g., no note about using it versus other search paths, or about what to do when the search is too narrow).

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