Skip to main content
Glama
ferasbbm

Sportmonks MCP Server

by ferasbbm

get_fixtures_head_to_head

Retrieve head-to-head fixtures between two teams by providing their IDs.

Instructions

Get head-to-head fixtures between two teams.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team1_idYesFirst team ID.
team2_idYesSecond team ID.
includeNoSemicolon-separated includes. Available: sport;round;stage;group;aggregate;league;season;coaches;tvStations;venue;state;weatherReport;lineups;events;timeline;comments;trends;statistics;periods;participants;odds;premiumOdds;inplayOdds;prematchNews;postmatchNews;metadata;sidelined;predictions;referees;formations;ballCoordinates;scores;xGFixture;pressure;expectedLineups;predictedLineups;matchfacts
selectNoComma-separated fields to return on base entity.
filtersNoFilters. e.g. fixtureLeagues:501,271 or fixtureStates:1 or markets:12,14
sortByNoField to sort by. e.g. starting_at
localeNoLanguage for name fields. e.g. en, de
timezoneNoTimezone for datetime fields. e.g. Europe/London
pageNoPage number for paginated results.
per_pageNoResults per page (max 50).
Behavior2/5

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

The description does not disclose any behavioral traits beyond the basic operation; no annotations exist, so the description carries the full burden but fails to mention pagination, rate limits, or data freshness.

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?

The description is very concise at one sentence, but it could include more useful information without being verbose.

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

Completeness2/5

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

Given the complexity of 10 parameters and no output schema, the description is incomplete; it does not explain return values, default behavior, or any constraints.

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% with basic descriptions for all parameters; the tool description adds no additional meaning beyond what the schema already provides, resulting in baseline score.

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?

The description clearly states the tool gets head-to-head fixtures between two teams, which is distinct from sibling tools like get_fixtures_by_date or get_fixture_by_id.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives; no prerequisites or context about when head-to-head data is available.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ferasbbm/sportmonks-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server