Skip to main content
Glama

Shot Quality & xFG (Pro)

shot_quality
Read-onlyIdempotent

Use this when the user asks about the quality of an NBA player's or team's shots, expected field-goal percentage (xFG%), who makes more or fewer shots than expected, or the quality of shots a defense allows. Returns, for a player_id, his season's attempts, FG% against xFG%, eFG% against xeFG%, three-point rate, shot making (points over expected per 100 shots) and his rank in it; for a team_id, the same for its offense and for the shots its defense allowed; with neither, the season's best and worst shot makers (200+ attempts). Requires Keel Stats Pro; the answer says so when the account has none. Not for box-score shooting splits: use player_profile.

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": "shot_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRegular season (default) or playoffs.
leagueNoLeague: "nba" (shot quality is modelled for the NBA).nba
seasonNoOptional season year. Defaults to the latest season with games played.
team_idNoOptional numeric team ID from search.
player_idNoOptional numeric player ID from search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the Keel Stats Pro entitlement requirement and that the answer reports missing access. It also lists returned fields and the fallback aggregation with neither player nor team, which is significant for a tool without an output schema.

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?

It front-loads usage and keeps every clause functional, with no filler. The return section is a dense multi-clause sentence that could be easier to scan, but the overall structure is logical.

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?

No output schema exists, so the description carries the burden of return-value disclosure and does so across all three call shapes. The Pro entitlement requirement and sibling exclusion complete the operational picture for an agent.

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?

Schema coverage is 100%, so the baseline is 3; the description adds conditional meaning by explaining that player_id returns player season metrics, team_id returns offense and defense-allowed metrics, and neither returns season leaders. It does not re-explain type, league, or season, but the schema already documents those parameters.

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?

The description opens with a specific use condition and names the exact metrics (xFG%, eFG%, shot making) and object (NBA player/team shots). It explicitly excludes box-score shooting splits and routes to player_profile, so it is clearly distinguishable from siblings.

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?

It states when to use ('user asks about the quality... xFG%...'), when not to use ('Not for box-score shooting splits: use player_profile'), and how player_id, team_id, or neither changes the answer. This is explicit routing guidance.

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