Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

sportsdb: Get league list

sportsdb_get_league_list
Read-onlyIdempotent

Retrieve a list of sports leagues, with optional filters by country and sport, to find specific competitions.

Instructions

List all leagues, optionally filtered by country and/or sport.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportNoSport name to filter by (e.g. 'Soccer')
countryNoCountry name to filter by (e.g. 'England')
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds context about the list scope and filtering, which is consistent with the annotations. No contradictions.

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 sentence that is front-loaded with the core action ('List all leagues') and efficiently conveys the optional filters. No wasted words.

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?

The tool is simple with no output schema and no required parameters. The description adequately covers its functionality, though it could hint at the output type (e.g., league names).

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 descriptions for both parameters. The description mirrors the schema without adding extra meaning. Baseline 3 is appropriate.

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 verb ('List'), resource ('all leagues'), and optional filters ('by country and/or sport'). It distinguishes itself from sibling tools like sportsdb_get_standings or sportsdb_get_sports_list.

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?

The description implies usage when needing a list of leagues, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it or any prerequisites.

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/lacausecrypto/mcp-sports-hub'

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