Skip to main content
Glama

Head to head

get_head_to_head
Read-onlyIdempotent

Use for two clubs' meetings in this competition in our data, which starts in 2001-02 in the oldest leagues: wins, draws and goals each, the first meeting we hold, and the results newest first. Costs 2 credits.

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": {
      "team": "<team>",
      "opponent": "<opponent>"
    },
    "name": "get_head_to_head"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamYesClub id, abbreviation or name.
limitNoMax results listed (default 20); the summary counts every meeting.
leagueNoLeague. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
opponentYesThe other club.

Output Schema

NameRequiredDescriptionDefault
noteNo
countYes
gamesYes
teamsYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely non-structured context: the data begins in 2001-02 and only for the oldest leagues, output is ordered newest first, and the call costs 2 credits. A rate/cost disclosure plus a data-coverage caveat is exactly the kind of context annotations cannot carry, though it does not mention failure modes for unknown clubs.

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

Conciseness5/5

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

A single dense sentence with the use case front-loaded and zero filler; the credit cost is appended last where it belongs. The clause stacking ("wins, draws and goals each, the first meeting we hold") is slightly awkward but nothing is redundant.

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?

An output schema exists, so return shape need not be explained, and the description still covers data coverage limits, ordering, and cost. For a 4-parameter read tool this is nearly sufficient; only guidance on unmatched club names or empty head-to-head results is missing.

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 100%, including the useful note that limit caps listed results while the summary counts every meeting, so the schema already does the heavy lifting. The description reinforces ordering ("results newest first") and the competition scope, but adds no syntax or matching rules for team/opponent beyond what the schema states. Baseline 3 applies.

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 the resource precisely (two clubs' meetings in this competition) and enumerates the payload: wins, draws, goals each, first meeting held, results newest first. It is distinguishable from siblings like get_events or list_games because it is explicitly a two-club aggregate rather than an event list. It stops short of a clean verb+resource phrasing, reading more like a sentence fragment.

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?

"Use for two clubs' meetings" is an implied usage cue, but no alternatives are named or excluded — an agent must infer on its own whether get_events or get_game is a better fit for a single fixture. No prerequisites or edge conditions for choosing this tool are stated.

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.