Skip to main content
Glama
MSS23

Padel Finder MCP Server

by MSS23

book_court

Initiates a multi-step checkout flow to book a padel court slot by providing venue, time, duration, and price details.

Instructions

Start booking process for a padel court slot with interactive checkout wizard. Opens a multi-step checkout flow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceYesPrice of the booking
currencyNoCurrency codeEUR
venue_idYesThe venue ID
court_nameNoName of the court
start_timeYesStart time in ISO 8601 format (e.g., "2026-01-31T19:00:00Z")
venue_nameYesName of the venue
duration_minutesYesDuration of the booking in minutes
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions a multi-step checkout flow implying interactivity, but it doesn't disclose side effects (e.g., holds a slot), whether it's idempotent, or what happens on subsequent steps.

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?

Two clear sentences with no waste, but the second sentence ('Opens a multi-step checkout flow') largely restates the first. Could be more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters and no output schema or annotations, the description is incomplete. It does not explain return values, what happens after checkout starts, or how the agent should proceed.

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 baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it starts a booking process and opens a checkout wizard, but it's vague about what exactly the tool accomplishes (e.g., does it create a reservation?). It doesn't clearly distinguish from sibling tools like quick_book_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as quick_book_check or check_availability. No prerequisites or context for invocation are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MSS23/padel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server