Skip to main content
Glama
Sign In

Awning

by help.awning
OverviewDiscussionsAdmin

Check free time

get_availability
Read-only

Real free time for one offering. Slots mode returns start times; sessions mode returns classes with seats left; period mode (rentals) checks from/to and units left. Always call this instead of guessing from opening hours. Use it before create_hold, once the user has picked an offering and a day; it reserves nothing. Not for the business's weekly hours (those are in get_business).

Input Schema

NameRequiredDescriptionDefault
toYesWindow end (slots, sessions) or return time (period). ISO 8601. With an offset it is absolute; without an offset it is local time of the business (e.g. 2026-09-18T15:00).
qtyNoUnits to rent (period mode). Default 1.
fromYesWindow start (slots, sessions) or pickup time (period). ISO 8601. With an offset it is absolute; without an offset it is local time of the business (e.g. 2026-09-18T15:00).
optionsNoExtras the user chose, from the offering's `options` in get_business: [{"id":"deep_conditioning","value":true}]. `value` is true/false for yes-no extras, a number for quantities, a string for choices. Leave out to book without extras.
party_sizeNoHow many people the booking is for. Default 1; offerings with a larger minimum group need it set.
offering_idYesThe service, class or rental to check: offerings[].offering_id from get_business or search_businesses
resource_idNoOnly this staff member, room or unit: an id from the `resources` of an earlier answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / offering_id / description
      Added value: +"The service, class or rental to check: offerings[].offering_id from get_business or search_businesses"
    • changedInput schema / properties / options / description
      Previous value: -"Selected extras from get_business, e.g. [{\"id\":\"deep_conditioning\",\"value\":true}]"New value: +"Extras the user chose, from the offering's `options` in get_business: [{\"id\":\"deep_conditioning\",\"value\":true}]. `value` is true/false for yes-no extras, a number for quantities, a string for choices. Leave out to book without extras."
    • addedInput schema / properties / party_size / description
      Added value: +"How many people the booking is for. Default 1; offerings with a larger minimum group need it set."
    • changedInput schema / properties / qty / description
      Previous value: -"Units to rent (period mode)"New value: +"Units to rent (period mode). Default 1."
    • changedInput schema / properties / resource_id / description
      Previous value: -"Only this staff member or place"New value: +"Only this staff member, room or unit: an id from the `resources` of an earlier answer"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false. The description adds useful behavioral context: it reserves nothing and explains what each mode returns, but it does not cover auth needs or error behavior.

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?

The description is four tight sentences with no waste, and the core purpose and mode behavior are front-loaded before the usage guidance.

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

Completeness5/5

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

For a seven-parameter, three-mode availability tool with no output schema, it explains the key return shapes per mode and the critical pre-call condition (reserves nothing). The fully documented schema covers the remaining parameter details.

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 seven parameters are documented in the schema. The description only hints at mode-to-parameter mapping (from/to for period mode) and does not add meaningful parameter semantics beyond the schema.

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 states a specific action and resource: checking real free time for one offering. It also clearly distinguishes the three modes (slots, sessions, period) and explicitly separates this from get_business weekly hours.

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

Usage Guidelines5/5

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

It gives explicit timing and alternatives: use before create_hold once an offering and day are chosen, it reserves nothing, and it is not for weekly business hours, which are in get_business. The agent is told both when to use it and when not to.

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

All Awning toolsInspect
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