Skip to main content
Glama

IRM Consulting & Advisory

Check consultation availability

check_availability
Read-onlyIdempotent

Open 30-minute slots for a free consultation with IRM over the next 1 to 7 days, read live from the calendar. Each slot has a scheduling_url that opens Calendly with that time pre-selected; the person confirms the booking there.

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
daysNoNumber of days to search (1 to 7). Default 7.
startNoFirst day to search, YYYY-MM-DD or ISO 8601 date-time. Default: now.
serviceNoOptional service id the consultation is about (attribution only).
timezoneNoIANA time zone for the local times, e.g. America/Toronto. Default America/New_York.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real value beyond them: slots are 30 minutes, data is read live from the calendar, and each slot carries a scheduling_url that pre-selects the time in Calendly, with confirmation happening there rather than in this tool. There is no output schema, so this return-shape context is doing meaningful work.

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, no filler, and the core scope (30-minute free consultation slots, 1-7 days, live calendar) is front-loaded before the scheduling_url detail. Every clause carries information an agent needs.

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?

For a zero-required-parameter, read-only lookup with fully documented schema and no output schema, the description covers what the tool returns (slots with scheduling_url) and where the transaction completes. It stops short of describing edge behavior such as an empty-availability response or how times are formatted.

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%, including enum values, defaults and the note that service is attribution-only, so the baseline is 3. The description reinforces the days window (1 to 7) and that times are local, but adds no syntax or constraint detail that the schema does not already provide.

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 names a specific verb and resource: it opens 30-minute free-consultation slots read live from IRM's calendar over a 1-to-7-day window. It implicitly separates itself from a booking sibling by stating the person confirms the booking on Calendly via the returned scheduling_url, but it never names an alternative tool explicitly.

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 implied by the scope statement (next 1 to 7 days, free consultation) and by the note that booking happens elsewhere, so an agent can infer this is the pre-booking lookup step. However, there is no explicit when-to-use/when-not guidance and no named alternative such as create_booking_link or get_pricing.

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