Skip to main content
Glama

QConsul LLC

Check availability

check_availability
Read-onlyIdempotent

List open 1-hour slots for Standard Hourly and the first Executive 1:1 Subscription session (Pacific Time, at least one week out) between optional ISO 8601 dates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRange end, ISO 8601.
fromNoRange start, ISO 8601.
serviceNoService id from list_services; defaults to standard-hourly. REQUIRED for subscriptions: pass executive-subscription to get subscription times (on or after January 18, 2027, and only times whose recurring day of week and time is open for 12 months). Standard Hourly times are not valid for prepare_booking with executive-subscription.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, closed-world operation, so the safety profile is covered. The description does add real behavioral context beyond them: Pacific Time, a one-week minimum lead time, 1-hour granularity, and the fact that only the first Executive subscription session is returned. It does not disclose the return shape or how many slots come back.

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?

A single front-loaded sentence with no filler; verb and resource come first. The parenthetical constraint stack is dense but each clause (timezone, lead time, date format) carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only availability query with no output schema, the description should say what a slot looks like and what happens when from/to are omitted. It states the dates are optional but not the default window, leaving a gap an agent must guess at before calling prepare_booking.

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 coverage is 100% and the property descriptions are already detailed, including the service enum's subscription rules. The description adds only the timezone and the one-week-out floor that implicitly constrains `from`, which is modest incremental value over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb (List) and resource (open 1-hour slots) and scopes it to two named services with concrete constraints (Pacific Time, at least one week out). It clearly separates Standard Hourly from the first Executive 1:1 Subscription session, though it never names a sibling tool to contrast with.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the discovery step preceding prepare_booking or confirm_booking, but the description never states when to call it versus those siblings or what to do with the results. The relevant warning (Standard Hourly times are invalid for executive-subscription bookings) lives in the schema, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources