Skip to main content
Glama

FastballAPI

Schedule

get_schedule
Read-onlyIdempotent

Use for upcoming games (next 1-30 days, default 7) with the median line across posted sportsbooks: moneylines, run line and total. 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
daysNo
teamNoTeam id or abbreviation.
leagueNoLeague. Defaults to mlb. One of: mlb, ncaabase.

Output Schema

NameRequiredDescriptionDefault
daysYes
countYes
gamesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds cost (2 credits) plus a clear statement that no wagering occurs and prices are informational. It does not cover result volume or paging for a potentially large schedule, which is the only remaining behavioral gap.

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?

Short and front-loaded, with the purpose first, the alternative second, and cost plus the no-wagering disclaimer last. Every sentence carries information, though the two trailing sentences are slightly detached from the core usage instruction.

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

Completeness5/5

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

With an output schema present, return values need not be explained; the description fills the remaining gaps an agent needs — time window, default value, cost, and the sibling to use for per-book detail. Nothing material for correct invocation 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 coverage is 67% and the schema already documents team and the league enum, while the description only adds the default of 7 days — a value not present in the schema and genuinely useful. It says nothing about team identifier format or league interplay beyond what the schema provides, so schema does most of the work.

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 games) along with the concrete payload: median line across posted books for moneylines, run line and total. It also names the sibling get_odds for the full per-book view, so an agent can distinguish the two without opening 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?

Explicitly scopes usage to a 1-30 day window (default 7) and routes the agent to get_odds when every book's line is needed. Both the when-to-use and the named alternative with its selecting condition are present.

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.