List bookable time slots for a business on a given date and party size. Offer the guest only slots where available is true.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | YYYY-MM-DD, in the venue's local calendar. | |
| slug | Yes | ||
| party_size | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It conveys a read-only list operation and the filtering behavior around 'available is true', which is useful. However, it does not mention response shape, edge cases, pagination, or explicitly state that it does not create a booking.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with the core action and followed by a practical instruction. Every sentence earns its place and there is no redundant filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple availability-listing tool, but with no output schema and no annotations, the description leaves out details about the returned slot structure and behavior when no slots are available. It gives enough to invoke correctly, but not complete clarity on the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 33%, so the description must compensate. It maps slug to 'a business', and mentions date and party size in context, providing some added meaning. However, it does not fully describe slug's source/format or party_size semantics beyond the schema's minimum.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List') and resource ('bookable time slots'), scoped by date and party size. The added instruction to only offer slots where available is true differentiates it clearly from sibling tools like create_booking and search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies when to use this tool: when checking what times can be booked for a business on a given date and party size. It does not explicitly name alternatives or exclusion conditions, but the context is clear and unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct actions, but fetch and get_business overlap by both returning business details and differ only in input type (id vs slug). An agent could be uncertain which to call when both are present.
The majority follow verb_noun naming, but fetch and search are bare verbs and fetch/get_business use different prefixes for similar operations. The overall pattern is still readable and mostly predictable.
Eight tools is a well-scoped set for a booking assistant: it covers business search, details, availability, booking management, and listing requests without unnecessary bloat. Each tool earns its place.
Core guest workflows are covered: search, business details, availability checks, create/check/cancel bookings, and requesting new listings. There is no direct update tool, but the documented cancel-and-recreate path makes this a minor gap rather than a dead end.