@qasperai/mcp-server

Official

by QasperAI

Overview Schema Related Servers Score Discussions

JavaScript

Remote

find_next_available_appointments

Read-only

Search local service businesses to find the next available bookable appointment for a requested service and location.

Instructions

Find the next available bookable appointment starts across matching local service businesses. Use this for requests like 'find me the next available boat trip' or 'who has the soonest dentist appointment'. 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.

Input Schema

TableJSON Schema

Name	Required	Description
`subCategory`	Yes	Exact ProfessionalProfileSubCategory enum value derived from the user's request (e.g. 'EventPlanner', 'Dentist', 'Therapist'). Required.
`serviceQuery`	Yes	Service or activity wording from the user, e.g. 'boat trip', 'therapy session', 'haircut'.
`startDate`	Yes	First local date to search from (YYYY-MM-DD). Use today's date when the user asks for the next available option.
`locationText`	No	Place name as the user said it. Pass null only for remote or nationwide service searches.
`countryCode`	No	ISO-3166 alpha-2 country code (e.g. 'GR', 'US', 'GB'). Set when deducible.
`latitude`	No	Latitude of the search location. Pass when the client has a map viewport or GPS position.
`longitude`	No	Longitude of the search location. Pass alongside latitude.
`radiusKm`	No	Search radius in kilometers, default 10.
`serviceMode`	No	Hard filter on how the business delivers service. One of: 'in_person', 'remote', 'service_area', 'nationwide'.
`attributeFilters`	No	Hard filter on vertical-specific attributes as a JSON object. Keys and values come from get_refinement_options.
`daysToSearch`	No	Number of calendar days to scan starting at startDate. Defaults to 14 and is clamped between 1 and 31.
`resultLimit`	No	Maximum number of available appointment matches to return. Defaults to 5 and is clamped between 1 and 20.

Tool Definition Quality

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds behavioral context by specifying that the response includes only businesses with direct booking support, matching service, and available slots - going beyond what annotations provide.

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 well-structured and front-loaded with purpose, followed by examples, caller instructions, and response filtering. Each sentence earns its place without fluff, though it could be slightly more concise.

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?

Given 12 parameters, 3 required, and no output schema, the description adequately explains what the tool returns (businesses with direct booking, matching service, available slots). It also provides caller guidance. While it doesn't detail default parameters, the schema covers those.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining that the agent extracts structured search fields similarly to search_businesses and passes wording in serviceQuery, providing meaningful context beyond the schema.

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 description clearly states the tool finds the next available bookable appointments across local service businesses. It provides specific examples ('find me the next available boat trip', 'who has the soonest dentist appointment') and explains the response criteria, distinguishing it from general business search.

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?

The description explicitly tells when to use the tool ('use for requests like...') and how the agent should extract search fields. While it doesn't explicitly state when not to use it or mention alternatives, it provides clear context for usage.

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

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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/QasperAI/mcp-server'

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