Skip to main content
Glama

Tennis Control

Buscar torneos de tenis

search_tournaments
Read-onlyIdempotent

Search the public tennis tournament calendar of Tennis Control (www.tenniscontrol.es): national federations of 50+ countries, Tennis Europe, ITF Juniors, ATF, COSAT, COTECC, and professional tours (ATP, Challenger, WTA, ITF). Filter by country, region, category, circuit, dates, text or open registration. Returns dates, venue, categories, entry deadline and the official link where entries are made (Tennis Control never handles entries). Only tournaments ending today or later unless 'from' is given.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tournaments"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of date range (YYYY-MM-DD)
fromNoStart of date range (YYYY-MM-DD). Default: today
textNoFree text in name, venue or notes (e.g. a city or club)
limitNoMax results (default 25)
regionNoRegion or province, e.g. 'Cataluña', 'Madrid', 'Lombardia'. For Spain, autonomous communities
circuitNoCircuit code or name: te (Tennis Europe), itf (ITF Juniors), atf, cosat, cotecc, atp, chal, wta, wta125, itfp, isq (Spain iSQUAD), fat (Andorra), fitp, fft, dtb… Use list_circuits
countryNoCountry: name (Spanish or English) or code, e.g. 'España', 'Italy', 'FR', 'GER', 'AD'
categoryNoAge category: U10, U12, U14, U16, JR (U18), ABS (open/adults), or veterans V30…V80 ('V' = any veterans). Spanish names accepted (alevín, infantil, cadete, júnior, absoluto)
open_entriesNoOnly tournaments whose entry deadline has not passed yet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed domain), and the description adds real behavior beyond them: the default exclusion of past events, the fact that entries are never processed here, and which return fields to expect. Auth, rate limits and pagination behavior are not addressed, which keeps it short of a 5.

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?

Front-loaded with the purpose, then filters, then the return contract, in three efficient sentences. The long enumeration of federations and circuits is dense but does real work in establishing scope; nothing is redundant or self-referential.

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?

No output schema, but the description compensates by naming the returned fields (dates, venue, categories, entry deadline, official link). All nine parameters are documented in the schema and the coverage/scope of sources is stated. Only the result-set and pagination behavior (beyond 'limit') are left implicit.

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%, so the schema already documents all nine parameters including defaults, formats and examples. The description only reinforces which filter dimensions exist and adds the filtering semantics for the date range, adding modest value over structured data.

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?

States a specific verb+resource (search the public tennis tournament calendar of Tennis Control), names the exact data sources covered, and enumerates what filters and returns are available. It is clearly distinguishable from get_tournament (detail lookup) and list_circuits/list_countries (reference lists), the latter of which it explicitly routes to.

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?

Gives clear operating context: it searches only the public calendar, it never handles entries, and it excludes already-finished tournaments unless 'from' is supplied. It also points to list_circuits for circuit codes. It does not explicitly say when to prefer get_tournament for a single event, but the search-vs-detail split is inferable and the guidance present is concrete.

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.

Resources