Skip to main content
Glama

Injury reports

get_injuries
Read-onlyIdempotent

Current third-party injury reports for NBA, NFL, NHL and WNBA.

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_injuries"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam
afterNoAlias for cursor
limitNoPage size. Oversized valid limits are clamped.
cursorNoCursor returned in meta.next_cursor
leagueNoSport code
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond that: the data is 'current' (freshness expectation) and 'third-party' (source reliability caveat). It says nothing about pagination behavior, what a report record contains, or what happens when league is omitted.

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?

A single front-loaded sentence fragment with zero padding or redundancy. It is as short as possible, though the missing verb makes it read as a label rather than an instruction, and there is no structure to speak of because there is only one clause.

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

Completeness3/5

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

With six all-optional parameters, an agent needs to know what a bare call returns (all leagues? all teams?) and what fields an injury report carries, and the description answers neither. Annotations cover the safety profile and the schema covers the parameters, but the core output shape and default-scope behavior remain undocumented with no output schema to compensate.

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 every parameter including the unusual user_request field is documented in the schema itself. The description adds no meaning beyond that — no example league codes, no explanation of how team filtering interacts with league, and no note on the after/cursor alias. Baseline 3 is appropriate.

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 names a specific resource ('third-party injury reports') and scopes it to four leagues (NBA, NFL, NHL, WNBA), with 'Current' signaling freshness. It lacks an explicit verb and any differentiation from siblings, but among the listed siblings no other tool plausibly returns injury data, so an agent can still route correctly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of what this tool is not for, and no mention of alternatives. An agent must infer from the name alone that this is the injury-data source, and nothing tells it whether to prefer this over general stats tools when a user asks about a player's status.

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