Skip to main content
Glama

Team Profile, Ratings & Roster

team_profile
Read-onlyIdempotent

Use this when the user asks about one team's season: its record, ratings, roster, recent and coming games. Returns the record, offensive/defensive/net rating (NFL: EPA per play and success rate) with league ranks, the roster, the last and next games with their game_id, NBA play types against the league's points per possession and the NFL depth chart with its changes this week. Not for the whole league's standings (rankings_and_ratings) or two teams' history (head_to_head).

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>",
      "team_id": "<team_id>"
    },
    "name": "team_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueYesLeague ("nba" or "nfl").
seasonNoOptional season year. Defaults to the current season.
team_idYesNumeric team ID from the search tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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, so the safety profile needs no repeating. The description adds genuinely useful behavioral context beyond that: the exact metric definitions (NFL EPA per play and success rate, NBA play types vs league points per possession), inclusion of league ranks, and that depth-chart changes are scoped to "this week". It doesn't say whether a team with no games yet errors or returns partial data, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences: trigger first, then payload contents, then exclusions — a front-loaded, scannable structure with no filler. The dense return-value sentence carries real information rather than restating the name.

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 no output schema, the description has to carry the return-shape burden and does: record, ratings with ranks, roster, last/next games with game_id, NBA play types, NFL depth chart deltas. Combined with full schema coverage for a 3-parameter tool, an agent has everything needed to call it and interpret results.

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% with descriptions on all three parameters including the enum and the season default, so the schema does the heavy lifting and baseline 3 applies. The description adds only the implication that results are season-scoped, without clarifying season format or team_id sourcing beyond what the schema already says.

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?

Names a specific verb+resource ("one team's season: its record, ratings, roster, recent and coming games") and enumerates the contents, so an agent can distinguish it from rankings_and_ratings and head_to_head without opening the schema.

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 states the triggering condition ("Use this when the user asks about one team's season") and names two exclusions with their correct alternatives: league-wide standings go to rankings_and_ratings, two-team history to head_to_head. Nothing about routing is left to inference.

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