Skip to main content
Glama
Sign In
APIbase

APIbase

by whiteknightonhorse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Football Leagues

sports.football.leagues
Read-onlyIdempotent

Search football leagues and cups by country or name. Get league ID, name, type, country, and logo for use in fixtures and standings queries.

Instructions

Search football leagues and cups by country or name. Returns league ID, name, type (league/cup), country, logo. Use IDs for fixtures and standings queries (API-Sports)

Input Schema

NameRequiredDescriptionDefault
searchNoSearch league by name (e.g. "Premier", "Champions")
countryNoCountry name to filter leagues (e.g. "England", "Spain", "Germany")

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0
  2. Removedv1.0.20
  3. Addedv1.0.15
  4. Removedv1.0.14
  5. Addedv1.0.10

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint (true), destructiveHint (false), idempotentHint (true). The description adds return field details but no behavioral traits beyond what annotations imply. 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?

Two sentences, front-loaded with purpose and return fields, no wasted words. Efficiently conveys essential information.

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?

Given the output schema exists and annotations are rich, the description sufficiently covers return fields and connects to sibling tools. No gaps for a search tool.

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?

Input schema has 100% coverage with clear descriptions for both parameters. The description repeats 'country or name' but adds no new semantic details. 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 tool searches football leagues and cups by country or name, specifies return fields (ID, name, type, country, logo), and hints at usage with sibling tools. This distinguishes it effectively from sports.football.fixtures and sports.football.standings.

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?

The description explains to search by country or name and recommends using IDs for fixtures and standings queries. While it doesn't explicitly list when not to use it, the context is clear enough for an AI agent.

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

Deploy Server

Other Tools