Skip to main content
Glama

Padel Stay Guide

Search hotels with padel courts

search_padel_hotels
Read-onlyIdempotent

Searches hotels and resorts with padel courts by place, number of courts, court type, coaching, guest access and more. Use it when someone wants somewhere to stay and play padel. Filters match stated facts: a hotel matches a filter when a source we read states that fact. Returns the number of matches, the top hotels with links, and a link to the full list on the site.

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_padel_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNodocumented (default): best documented first. courts: most courts. checked: most recently verified.
textNoWords to find in the hotel name, city, region or country, e.g. "Marbella".
limitNoHow many hotels to return, default 5.
accessNofree: included for guests. paid: court time costs extra.
regionNoRegion in that country, e.g. "Costa del Sol". Needs country.
countryNoCountry name, e.g. "Spain" or "UK".
coachingNotrue for properties stated to offer padel coaching.
court_typeNo"both": the property has indoor and outdoor courts.
min_courtsNoAt least this many padel courts.
property_typeNoKind of property.
min_confidenceNohigh: the property's own site states the court. medium: a directory and the property's site both mention padel.
bookable_onlineNotrue for properties with an online booking link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, non-open-world search, so safety is covered. Beyond that, the description adds genuinely non-obvious behavior: filters are strict stated-fact matches ('a hotel matches a filter when a source we read states that fact'), implying absent features may mean undocumented rather than missing, and it spells out the response contents. It does not cover result limits or pagination behavior, which the schema handles.

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 sentences ordered purpose → when to use → behavior and returns, with the key constraint front-loaded in sentence three. The phrase 'and more' after the filter list is the only minor filler; otherwise no sentence is redundant.

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?

For a 12-parameter, zero-required search tool with no output schema, the description supplies purpose, when-to-use, matching semantics, and return contents, so an agent can call it correctly. Remaining gaps (default result count, behavior on overly narrow filters) are covered or implied by the schema defaults and the stated-fact rule.

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% with per-enum explanations, so the baseline is 3, and the description clears that bar by explaining that every filter operates on documented facts rather than inferred ones. That shared matching rule changes how an agent should interpret zero-result filters across all 12 parameters, which the schema alone does not convey. It adds no per-parameter detail beyond the schema, which is fine given the coverage.

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?

States a specific verb and resource ('Searches hotels and resorts with padel courts') and enumerates the filter axes (place, courts, court type, coaching, guest access). It also describes the return shape (match count, top hotels with links, link to full list), which implicitly separates it from a single-hotel lookup, but it never names a sibling tool.

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 an explicit use case: 'Use it when someone wants somewhere to stay and play padel,' which is a clear selection signal for a travel-plus-activity query. It offers no when-not guidance and does not point to get_padel_hotel for drilling into a specific property, so exclusions are left to inference.

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