Skip to main content
Glama

Get Match Shooting

get_match_shooting
Read-only

Retrieve shot zones and per-player shooting attempts for a completed match when a detailed team analysis is requested.

Instructions

Shot zones and per-player attempts for a finished match. Use only when explicitly asked for a detailed analysis of a team.

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": {
      "match_id": "<match_id>"
    },
    "name": "get_match_shooting"
  }
}

Input Schema

NameRequiredDescriptionDefault
match_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, and an output schema exists so return values need not be explained. The description does add one genuinely useful behavioral constraint — the match must be finished — but says nothing about coverage (both teams? all players?) or behavior when the match is unfinished.

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?

Two front-loaded sentences with no wasted wording. The second sentence is slightly awkward — 'detailed analysis of a team' reads like generic scoping rather than being tied to the shot-zone data described just before it.

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?

For a one-parameter, read-only tool that has an output schema, the definition covers what it returns and when to reach for it. The remaining gap is minor: whether results span both teams and what happens for a non-finished match.

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 0% and the single required match_id is never mentioned in the description. It is self-evident from the name, and 'for a finished match' at least implies match_id must reference a completed match, which is a real semantic constraint, but nothing about format or source of the ID is added.

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?

Names the resource precisely — shot zones plus per-player attempt counts for a match — which is distinguishable from get_match, get_match_events, and get_boxscore by the specific data it returns. There is no explicit verb, but the returned content is concrete enough for an agent to know what it gets.

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?

'Use only when explicitly asked for a detailed analysis of a team' is an explicit gating condition rather than generic filler, which helps an agent avoid calling it by default. It stops short of naming an alternative lightweight tool (e.g. get_boxscore) for the non-detailed case, so routing is only half-specified.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.