Skip to main content
Glama

What a team allows

get_opponent_stats
Read-onlyIdempotent

What a team gives up per game to opposing teams, or by=position for what each position records against it. Needs league, one of meta.stats_leagues. Send team, or a season to read every team. Set end_date to read it as of a past day. Free plan: one team, its last 10 games.

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": {
      "league": "<league>"
    },
    "name": "get_opponent_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoteam or position.team
dateNoOne game date, league local.
lastNoThat team's most recent N games, as one row with season null. Needs team.
teamNoThe team whose defense you are reading: a code (BOS) or team id (tm_...).
limitNoTeams per page: up to 100 with by=team, up to 10 with by=position.
cursorNometa.next_cursor from the preceding page. Send the same filters.
leagueYesLeague code, for example NBA. meta.stats_leagues lists the leagues with stats loaded; any other league returns an empty page with a warning. A segment league from a projection row (NBA1Q) reads as its full league. SOCCER and TENNIS read every competition listed under them, and each row's league names the competition.
seasonNoSeason label, as listed in meta.coverage.seasons: 2025-26, or 2026 in single-year leagues.
end_dateNoGames on or before this league-local date. For a feature as it stood before a game, set this to the day before.
positionNoby=position only: return one position.
start_dateNoGames on or after this league-local date.
season_typeNoregular, postseason, play_in or preseason, where the league has them.
user_requestNoOptional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the free-plan cap, that an unknown league returns an empty page with a warning, that a segment league code like NBA1Q resolves to its full league, that SOCCER/TENNIS span every competition with the competition named per row, and that last=N collapses to a single row with season null.

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?

Four short sentences, front-loaded with the core meaning and then progressively the constraints, with no filler. The telegraphic style ('Needs league, one of meta.stats_leagues') is dense but readable and each clause carries a distinct operational fact.

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?

For a 13-parameter, multi-mode stats tool with no output schema, the description covers the read modes, the league vocabulary, point-in-time semantics, pagination-adjacent constraints and plan limits. The remaining parameters are fully documented in the schema, and safety is covered by annotations, so nothing critical is left for the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the floor is 3, and the description earns above that by explaining parameter interplay the schema states only piecewise: team vs. season as the two read modes, by=position as a separate axis, and end_date's 'day before the game' trick for pre-game features. It omits start_date and season_type, but those are already self-documenting in the schema.

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 opening sentence states a specific resource and measure: what a team 'gives up per game to opposing teams', with a by=position variant. That is concrete enough to distinguish it in spirit from get_team_stats (own production vs. opponents' production against this team), but the sibling is never named, so the agent must infer the contrast from the domain wording alone.

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?

It gives clear operating guidance: league is mandatory and must come from meta.stats_leagues, send team for one team or a season to read every team, use end_date to read as of a past day, and free-plan users are limited to one team's last 10 games. What is missing is an explicit 'use get_team_stats instead when you want the team's own numbers' routing statement.

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.

Resources