Skip to main content
Glama

SportStatsAPI

by com.sportstatsapi
OverviewDiscussionsAdmin

get_match_briefing

Read-only

Ready briefing for one match (any sport but cricket): form, current streaks, home and away records, head-to-head, table position and gaps, stakes, schedule; for soccer also injuries, lineups, players one league appearance or goal short of a club milestone (milestone_next) and, after the match, the story (comeback, late winner, red cards), runs it ended (streak_ended_*: 'first defeat after 11 unbeaten') and long waits it ended that our data can date (first_since_*: first win at the opponent's ground, first clean sheet, top of the table for the first time since a day; history_from: nothing is claimed before it). The head-to-head block has goals and each side's biggest win. Soccer before kickoff: players suspended (suspended_out) or one booking from a ban, by the league's card rules. Each statement also as a sentence (lang de, es, it, fr), and summary: the most important sentences as one paragraph in that language. Facts only, no predictions. Insights feature. Prefer this for 'tell me about this match'.

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
sportNosport (default soccer; see list_sports)
formatNomd for a short Markdown text instead of JSON
match_idYesmatch code (or number) from get_matches

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / match_id / description
      Previous value: -"match id from get_matches"New value: +"match code (or number) from get_matches"
  2. Changed1 schema field changed
    • changedInput schema / properties / match_id / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "string"
+]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this as a read-only, non-open-world operation, and the description adds meaningful behavioral context: facts only, no predictions, language support, post-match narrative constraints, and the history_from data boundary. It does not cover permissions or rate limits, but those are less relevant for a read-only briefing tool.

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 description is front-loaded with the core purpose, but it becomes a long run-on enumeration of content blocks and output variants. Much of the detail is valuable for a tool with no output schema, yet the structure could be clearer and more concise.

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 and a complex briefing tool, the description is thorough about what the briefing contains, how language and format are handled, and what limitations apply. An agent has enough information to understand the return content and call the tool correctly.

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%, so the schema already documents lang, sport, format, and match_id. The description adds minor context such as 'any sport but cricket' and language availability, but it mostly repeats what the schema already provides. Baseline 3 is appropriate.

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 states a specific resource and scope: a ready briefing for one match, covering all sports except cricket, with detailed content areas. It does not explicitly differentiate itself from close siblings such as get_match or get_match_details, leaving the agent to infer that this is the comprehensive briefing variant.

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?

It gives a clear usage cue: 'Prefer this for tell me about this match,' and distinguishes pre-match soccer content from post-match story content. It does not state when to choose get_match_details or get_match instead, so alternatives are only implied.

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

All SportStatsAPI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources