Book It

Check request windows

check_availability

Read-onlyIdempotent

List the windows a Book It business accepts booking requests for, by date in the business's time zone, after its minimum notice and without its days off, for up to 14 days at a time. Each window has a window_id for request_booking. A window is when the business says it can take work, not a confirmed slot.

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": {
      "business_id": "<business_id>"
    },
    "name": "check_availability"
  }
}

Input Schema

Name	Required	Description
`days`	No	How many days to show, 1 to 14. Defaults to 7.
`from_date`	No	First date to show, YYYY-MM-DD, in the business's time zone. Defaults to today there.
`business_id`	Yes	The business_id exactly as find_provider returned it, such as "juniper-ridge-roofing".

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral detail beyond them: results are already filtered by the business's minimum notice and days off, and dates are resolved in the business's time zone. It also clarifies that a returned window is availability, not a confirmed booking — a semantic distinction the annotations cannot convey.

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?

Two sentences, front-loaded with the core action and scope, then a short clarification of the return value. Nothing is redundant with the schema or annotations, and every clause carries information.

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?

With no output schema, the description carries the burden of explaining returns, and it does identify the key field (window_id) and the meaning of a window. It does not describe what else a window contains or how results are ordered/paginated, which leaves a small gap for a list-returning tool.

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 all three parameters (including defaults for days and from_date and the YYYY-MM-DD format) are already documented. The description reinforces the 14-day cap and time-zone framing but adds no new syntax or constraint detail beyond the schema, so the baseline 3 applies.

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 verb and resource ('List the windows a Book It business accepts booking requests for') and immediately ties the result to a sibling ('Each window has a window_id for request_booking'). It also disambiguates the concept from a confirmed slot, so an agent can tell it apart from request_booking without opening either schema.

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?

Clear context: call this to see bookable windows and then pass a window_id to request_booking, which is explicit routing. It does not state when NOT to use it (e.g., versus quote_range or get_services) or any prerequisite ordering beyond the business_id lookup hint, so it stops short of full when/when-not guidance.

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

All Book It 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?