Skip to main content
Glama
ferasbbm

Sportmonks MCP Server

by ferasbbm

get_referees_by_country_id

Retrieve referees from any country by providing the country ID. Use includes, filters, and pagination to customize results.

Instructions

Get referees from a specific country.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_idYesCountry ID.
includeNoSemicolon-separated includes. e.g. country;season;statistics
selectNoComma-separated fields to return.
filtersNoFilters to apply.
localeNoLanguage for name fields.
pageNoPage number.
per_pageNoResults per page.
Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits like pagination, sorting, or the effect of optional parameters. It only states a basic purpose.

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?

Extremely concise at one sentence, but lacks structure such as bullet points or separation of key points. It is front-loaded with purpose but sacrifices completeness.

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?

Despite having 7 parameters and no output schema, the description provides minimal context. It does not explain how to use optional parameters like include, select, or pagination, leaving significant gaps for the agent.

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%, so the schema already explains all parameters. The description adds no additional meaning beyond the country_id implied by the tool name. Baseline score of 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?

Description clearly states the tool retrieves referees filtered by country, matching the tool name. However, it does not explicitly distinguish it from sibling tools like get_all_referees or get_referees_by_season_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 such as get_all_referees or search_referees_by_name. The description provides no context for usage decisions.

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