Skip to main content
Glama

get_availability

Check when staff, rooms, or resources are free within a date window, considering bookings, holidays, and work times. Returns free slots and fully-free days, and indicates if a required duration fits.

Instructions

Check when staff, rooms (suites) or resources are FREE in a date window (default 14 days, max 92). Considers bookings, public holidays and staff absences/work times. Returns free time slots and fully-free days per entity, and whether a required duration fits. Select entities with search/site/status (names from find_resources).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoWindow end, YYYY-MM-DD (inclusive).
daysNoWindow ends this many days after start, inclusive (alternative to 'to'). Default 14.
fromNoWindow start, YYYY-MM-DD. Default today.
siteNoSuites only: limit to suites whose site name contains this.
typeYesKind of entity to check. 'site' checks every suite of sites whose name matches search.
staffNoStaff type only: internal or external. Omit for both.
weeksNoWindow length in weeks (overrides 'days').
searchNoOnly entities matching this name/number/title. Omit for all.
statusNoEntity status. Default active.
durationNoRequired free length. Needs duration_unit.
duration_unitNo'minutes'/'hours' need one contiguous free slot of that length; 'days' needs that many fully-free days.
Behavior4/5

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

The description transparently explains what the tool considers (bookings, holidays, absences) and what it returns (free slots, fully-free days, duration fit), compensating for lack of annotations.

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 dense, informative sentences with no wasted words. First sentence covers purpose and constraints, second covers outputs and parameter hints.

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 11 parameters and no output schema, the description covers main inputs and outputs well, though it could clarify parameter interactions (e.g., to vs days vs weeks).

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 baseline is 3. The description adds minimal extra context beyond the schema, such as linking to find_resources for entity names.

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 verb 'check' and the resources (staff, rooms, resources), and distinguishes from sibling tools like find_resources by specifying it checks availability within a date window.

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?

The description gives context on selecting entities using search/site/status but does not explicitly state when to use this tool over alternatives or when not to use it.

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

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

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