Skip to main content
Glama

Padel Stay Guide

Get a hotel's padel details

get_padel_hotel
Read-onlyIdempotent

Gets one hotel's padel details: courts, indoor or outdoor, guest access, coaching, racket rental and season, how sure we are the court exists and when we last checked, plus its official website and booking links. Use it when someone asks about a specific hotel, or to follow up a search result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hotel": "<hotel>"
    },
    "name": "get_padel_hotel"
  }
}

Input Schema

NameRequiredDescriptionDefault
hotelYesThe hotel's slug or url from search_padel_hotels, or its name.

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 declare read-only, idempotent, closed-world behavior, so the bar is lower. The description adds real value beyond them by disclosing that the response includes a confidence signal ('how sure we are the court exists and when we last checked'), which warns the agent that returned data may be unverified or stale — a trait not captured by any annotation.

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 action and the returned field set, then the usage rule. Two sentences, no filler; the field enumeration is long but each item tells the agent what it can retrieve, so it earns its space.

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?

A single-parameter read tool with full schema coverage and no output schema; the description covers purpose, the returned content, provenance/confidence indicators, and invocation context. Minor gaps (pagination not relevant, error behavior for unknown hotel) are acceptable at this complexity.

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% and the single 'hotel' parameter already documents that it accepts a slug, URL from search_padel_hotels, or a name. The description adds no further parameter meaning (e.g., name matching behavior or ambiguity handling), so baseline 3 applies.

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 ('Gets one hotel's padel details') and enumerates the returned fields — courts, indoor/outdoor, guest access, coaching, racket rental, season, confidence and last-checked date, website and booking links. It clearly reads as a single-hotel detail lookup, distinct from the sibling list/search tools.

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 explicit triggers: 'when someone asks about a specific hotel, or to follow up a search result.' That covers the main when-to-use case and implicitly contrasts with search_padel_hotels, though it doesn't state exclusions (e.g., use the list tool for multi-hotel or destination-level questions).

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