Skip to main content
Glama

qasper

by io.github.QasperAI

find_next_available_appointments

Read-only

Find the next available bookable appointment starts across matching local service businesses. Use this ONLY when the user explicitly asks for availability, booking, the soonest appointment, or a specific appointment time. Examples: 'book me a dentist', 'who has availability tomorrow?', 'find the soonest groomer appointment', 'get me a dermatologist next Wednesday'. Do NOT use this for generic discovery requests like 'find me a dentist in Paris' or 'show me pet groomers near me'; use search_businesses for discovery. The CALLER (you, the agent) extracts the structured search fields the same way as search_businesses, and passes the service or activity wording in serviceQuery. The response only includes businesses with direct booking support, a matching service, and at least one slot whose bookingStartPolicy and remainingCapacity allow booking. An empty result does NOT mean no matching businesses exist; it only means no directly bookable matching slots were indexed. If this returns no results, call search_businesses before responding to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeNoLatitude of the search location. Pass when the client has a map viewport or GPS position.
radiusKmNoSearch radius in kilometers, default 10.
longitudeNoLongitude of the search location. Pass alongside latitude.
startDateYesFirst local date to search from (YYYY-MM-DD). Use today's date when the user asks for the next available option.
countryCodeNoISO-3166 alpha-2 country code (e.g. 'GR', 'US', 'GB'). Set when deducible.
resultLimitNoMaximum number of available appointment matches to return. Defaults to 5 and is clamped between 1 and 20.
serviceModeNoHard filter on how the business delivers service. One of: 'in_person', 'remote', 'service_area', 'nationwide'.
subCategoryYesExact ProfessionalProfileSubCategory enum value derived from the user's request (e.g. 'EventPlanner', 'Dentist', 'Therapist'). Required.
daysToSearchNoNumber of calendar days to scan starting at startDate. Defaults to 14 and is clamped between 1 and 31.
locationTextNoPlace name as the user said it. Pass null only for remote or nationwide service searches.
serviceQueryYesService or activity wording from the user, e.g. 'boat trip', 'therapy session', 'haircut'.
attributeFiltersNoHard filter on vertical-specific attributes as a JSON object. Keys and values come from get_refinement_options.

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that responses only include businesses with direct booking support and slots meeting bookingStartPolicy/remainingCapacity criteria. It also clarifies that an empty result does not mean no businesses exist, only that no bookable slots were indexed, adding critical interpretation context.

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?

The description is longer than ideal (8 sentences), but every sentence serves a purpose: examples, exclusions, parameter guidance, response criteria, and fallback behavior. The primary purpose is front-loaded in the first sentence, and the length is justified by the tool's nuanced behavior.

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?

Given the absence of an output schema, the description explains response filtering criteria and empty-result interpretation. It covers when to use, how to extract parameters, what the response includes, and what to do when no results are returned, making it operationally complete for an agent.

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?

While schema coverage is 100%, the description adds operational meaning by instructing the caller to extract structured search fields the same way as search_businesses and to pass service/activity wording in serviceQuery. This cross-reference and explicit assignment of serviceQuery goes beyond the schema's field descriptions.

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?

The first sentence clearly defines the tool's purpose with a specific verb ('find') and resource ('next available bookable appointment starts') across local service businesses. It explicitly distinguishes itself from discovery tools like search_businesses by stating it should not be used for generic discovery, and provides concrete examples of triggering queries.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('ONLY when the user explicitly asks for availability, booking, the soonest appointment, or a specific appointment time') and when not to use it (generic discovery), naming the alternative tool (search_businesses). It also provides fallback instructions: if no results, call search_businesses before responding.

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

All qasper toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool targets a distinct action: discovery, refinement, business details, services, pricing, availability, booking, inquiry, and agent chat. Even the two availability tools are clearly separated by scope (specific business/service/date vs. cross-business soonest slots). No two tools appear to do the same thing.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (search_businesses, get_business_info, book_appointment, etc.). Verbs are varied but each is semantically precise, and there are no punctuation or style inconsistencies.

Tool Count5/5

With 10 tools, the server is well-scoped for its purpose: covering the full local-business discovery-to-booking journey. Each tool earns its place and there is no redundancy or bloat.

Completeness5/5

The tool surface comprehensively covers the domain: search, refinement, info, services, pricing, availability (both specific and cross-business), booking, inquiry, and agent interaction. There are no missing critical operations for the stated purpose of discovering, contacting, and booking local service businesses.

Resources