Skip to main content
Glama

Schedule

get_schedule
Read-onlyIdempotent

Use for upcoming fixtures (next 1-30 days, default 7) with the median three-way line across posted sportsbooks (home, draw, away moneylines, goal total, handicap) and its implied probabilities. For every book's line use get_odds. Costs 2 credits. Prices are market information; no tool places, accepts or tracks wagers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays ahead (default 7).
teamNoClub id, abbreviation or name.
leagueNoLeague. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.

Output Schema

NameRequiredDescriptionDefault
daysYes
countYes
gamesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the 2-credit cost, the fact that lines are medians across books rather than per-book, and the disclaimer that no tool places, accepts or tracks wagers — useful guardrails against misuse. It does not describe caching or pagination, so not a 5.

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?

Three sentences, front-loaded with the core purpose, followed by the alternative routing and the credit/wagering caveats. The closing disclaimer is slightly off-topic but justifies its place as an agent guardrail; otherwise there is 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?

An output schema exists, so return values need not be explained, and the description covers scope, window, cost and sibling routing. What is missing is only minor: how team/league filters interact with the median aggregation across books.

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 coverage is 100% and the schema already documents days, team and the league enum, so the description's restatement of the 1-30 day window adds little. Nothing is said about how team identifiers or league defaults affect the returned median line, so it does not exceed the schema baseline.

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 ('upcoming fixtures'), the window (1-30 days, default 7), and exactly what is returned (median three-way line, goal total, handicap, implied probabilities). It also explicitly distinguishes itself from get_odds, so an agent can separate the two without inspecting schemas.

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

Usage Guidelines5/5

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

Gives clear when-to-use guidance ('upcoming fixtures') and names the alternative for a different need: 'For every book's line use get_odds.' This is explicit routing to a sibling tool with the condition that selects it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.