Skip to main content
Glama

Padel Stay Guide

List padel destinations

list_padel_destinations
Read-onlyIdempotent

Lists the countries this site covers with the number of padel hotels in each, or the regions of one country. Use it to see where hotels with padel courts are listed, or to check a place name before searching. The names it returns work as country and region in search_padel_hotels.

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": "list_padel_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoA country, to list its regions. Leave out to list every country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the result is enumerated place names with hotel counts, and those names are the valid inputs for other tools, which tells the agent this is a cheap, safe discovery call.

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?

Three short sentences with the primary behavior front-loaded and the workflow hint last. There is mild overlap between 'Lists the countries...' and 'Use it to see where hotels... are listed,' but nothing wasteful enough to cut.

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?

For a one-parameter, read-only lookup with no output schema, the description covers behavior, both operating modes, and the shape/naming of returned values. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already documented, so baseline would be 3. The description goes further by conveying that values are country/region names originating from this tool itself, effectively defining the accepted value domain and the relationship between the two modes.

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 and resource ('Lists the countries this site covers with the number of padel hotels in each, or the regions of one country') and makes the two operating modes explicit. An agent can immediately tell this apart from search_padel_hotels, which finds hotels rather than enumerating places.

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 when-to-use guidance: 'to see where hotels with padel courts are listed, or to check a place name before searching,' which also positions it as a prerequisite step to search_padel_hotels. It stops short of an explicit negative case (e.g., when to skip it), so it lands just under the top score.

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