Skip to main content
Glama

Shot map

get_shot_map
Read-onlyIdempotent

Use for a shot map: a club's shots (or, with against, the shots it conceded), a player's, or one match's, for a season (default: the latest). Returns totals and zones (six-yard box, penalty area, outside the box, penalties) with goals, shots on target, xG and conversion, and every located shot with its x/y, end point, outcome and xG. Costs 10 credits.

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

Input Schema

NameRequiredDescriptionDefault
teamNoClub id, abbreviation or name.
leagueNoLeague. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
playerNoPlayer id (search_players).
seasonNoSeason by the year it starts (default: the latest).
againstNoWith team: the shots it conceded.
game_idNoOne match instead of a season.
include_shotsNofalse = totals and zones only.

Output Schema

NameRequiredDescriptionDefault
noteNo
shotsNo
zonesYes
seasonYes
totalsYes
goals_onlyNo
shots_noteNo
shots_totalYes
goals_only_noteNo
unlocated_shotsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / goals_only
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "goals": {
      +      "type": "number"
      +    },
      +    "matches": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "goals",
      +    "matches"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / goals_only_note
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description goes further by disclosing the 10-credit cost and the exact shape of returned content (totals, zones, per-shot coordinates). It doesn't mention rate limits or failure modes, but cost disclosure is a meaningful addition for a paid endpoint.

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?

One front-loaded sentence with the use case first, then scope, then return payload, then cost — no filler. It is dense and long-ish, but every clause carries information an agent needs to choose arguments.

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

Completeness4/5

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

Covers scoping, defaults, output contents and cost for a 7-parameter, zero-required tool; with an output schema present, it needn't detail return structure. Only minor gap is not clarifying how team+player combine or what happens when neither is supplied.

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 baseline is 3, but the description adds real meaning beyond it: it explains what 'against' produces (conceded shots), that season defaults to latest, and that results cover zones plus individual located shots. The include_shots toggle is only implied ('every located shot'), not spelled out as its trade-off.

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 ('Use for a shot map') and enumerates the three scopes (club, club-conceded, player, match) plus the default season. An agent can tell this apart from get_team_stats or get_player 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 Guidelines4/5

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

Gives clear selection context: which entity scopes map to which arguments, that 'against' flips to conceded shots, and that season defaults to the latest. It does not name an alternative tool for aggregate stats, so exclusions are left implicit.

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.