ekkor

booboooking_find_next_available

Read-onlyIdempotent

Search forward for the next available appointment slots for a provider and service on booboooking.com. Returns up to count openings sorted chronologically. Useful when you need "the next available appointment" without a specific date in mind.

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": {
      "provider": "<provider>",
      "service_id": "<service_id>"
    },
    "name": "booboooking_find_next_available"
  }
}

Input Schema

Name	Required	Description
`count`	No	Number of openings to return (default: 3, max: 10)
`provider`	Yes	Provider identifier
`from_date`	No	Start search from this date in YYYYMMDD format (default: today)
`service_id`	Yes	Service ID from booboooking_list_services
`search_days`	No	Days to search ahead (default: 30, max: 60)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral detail: it searches forward chronologically, returns up to `count` openings, and sorts results by time. No contradiction with annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all purposeful: first states the core action, second describes output behavior, third gives the use case. No filler, no repetition of schema information, and the most important info is front-loaded.

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 read-only search tool with full schema coverage and no output schema, the description captures the core semantics, result ordering, and primary use case. The only small gap is not explicitly naming the alternative for date-specific availability checks, but that is sufficiently implied.

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 description coverage is 100%, so every parameter is already documented with meaning and defaults. The description adds no new parameter-level detail beyond mentioning `count`; the schema carries the burden, so the baseline score of 3 is appropriate.

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 action ('search forward for the next available appointment slots'), the target resource (a provider and service on booboooking.com), and the key differentiating use case ('without a specific date in mind'). This clearly distinguishes it from date-specific sibling tools like check_availability.

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?

Explicitly says the tool is useful when the agent needs the next available appointment without a specific date, giving clear selection context. It doesn't name an alternative sibling or state when not to use it, but the guidance is sufficient for an agent to choose this over a date-specific lookup.

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

All ekkor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?