Skip to main content
Glama

Get Match

get_match
Read-only

Fetch match header data including teams, date, competition, and period scores by match ID; optionally include box score when available.

Instructions

Match header: teams, date, competition, score by period. Box score is not included until the match is overnds.

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

Input Schema

NameRequiredDescriptionDefault
match_idYes
include_boxscoreNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description's job is to add context. It does add one useful behavioral fact — the box score is withheld until the match is finished — but that statement is garbled and sits in slight tension with the include_boxscore parameter, whose interaction with the rule is never clarified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The definition is short and front-loads the field list, which is good. But the final sentence is corrupted ('overnds'), so it wastes the one line that carries the most useful behavioral information.

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?

An output schema exists, so return-value explanation is not required, and annotations cover the read-only safety profile. What is missing is any treatment of the two undocumented parameters and a clear resolution of when include_boxscore applies versus the 'not until match is over' rule.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description must compensate and does not. match_id is never mentioned, and include_boxscore is only obliquely referenced via the box-score sentence — an agent gets no guidance on what value to pass or when the flag overrides the stated rule.

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 ('Match header') and enumerates the fields it carries (teams, date, competition, score by period), which lets an agent distinguish it from the sibling get_boxscore. However, the trailing text is garbled ('overnds'), which slightly blunts the precision of the statement.

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

Usage Guidelines3/5

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

Guidance is only implied: the note that the box score is absent until the match ends hints that get_boxscore is the alternative for completed matches, but no explicit when-to-use or when-not-to-use rule is stated. An agent must infer the routing decision.

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