Skip to main content
Glama
Sign In

Awning

by help.awning
OverviewDiscussionsAdmin

Block or open time

owner_block_time
Destructive

Only for business owners signed in to Awning. Close time (day off, break, holiday) for the whole business or one staff member/room, or open extra time with open=true. Remove a block with remove_exception_id. Confirm with the owner first. Use it for one-off closures or extra hours; the regular weekly hours are set with owner_set_schedule. Bookings already in the blocked time are not cancelled: the answer lists them as existing_bookings_in_this_time.

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the block, same format; must be after `from`. Required unless removing a block.
fromNoStart of the block, ISO 8601; without an offset it is the business's local time, e.g. 2026-12-25T00:00. Required unless removing a block.
openNoTrue to open extra time outside the usual hours instead of closing time. Default false.
reasonNoA note for the owner, e.g. 'holiday'
business_idNoWhich business, when the owner runs several: business_id from owner_status. Leave out when there is only one.
resource_idNoOnly this staff member, room or rental pool: an id from owner_get_schedule. Leave out for the whole business.
remove_exception_idNoTake a block away: the exception_id from `blocked` in owner_get_schedule or from an earlier answer. Then `from` and `to` are not needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / business_id / description
      Previous value: -"Only needed if you manage several businesses"New value: +"Which business, when the owner runs several: business_id from owner_status. Leave out when there is only one."
    • addedInput schema / properties / from / description
      Added value: +"Start of the block, ISO 8601; without an offset it is the business's local time, e.g. 2026-12-25T00:00. Required unless removing a block."
    • addedInput schema / properties / open / description
      Added value: +"True to open extra time outside the usual hours instead of closing time. Default false."
    • addedInput schema / properties / reason / description
      Added value: +"A note for the owner, e.g. 'holiday'"
    • addedInput schema / properties / remove_exception_id / description
      Added value: +"Take a block away: the exception_id from `blocked` in owner_get_schedule or from an earlier answer. Then `from` and `to` are not needed."
    • addedInput schema / properties / resource_id / description
      Added value: +"Only this staff member, room or rental pool: an id from owner_get_schedule. Leave out for the whole business."
    • addedInput schema / properties / to / description
      Added value: +"End of the block, same format; must be after `from`. Required unless removing a block."
  2. Changed1 schema field changed
    • addedInput schema / properties / reason / maxLength
      Added value: +200
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive=true and non-idempotent, and the description adds material context beyond that: existing bookings in the blocked window are NOT cancelled but returned as existing_bookings_in_this_time, and how to undo a block via remove_exception_id. This is exactly the kind of side-effect disclosure an agent needs before a destructive call.

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?

Front-loads the action and scope, then the alternates, then the side effect. Dense but purposeful; the only mild redundancy is restating the open/remove_exception_id semantics already in the schema.

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?

Covers the destructive-write scenario fully: purpose, alternatives, permission gate (business owner signed in), and the returned field for conflicting bookings, which compensates for the absence of an output schema.

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%, so every parameter is already documented with format, defaults and interdependencies. The description echoes open=true and the remove_exception_id removal path but adds no syntax or constraint detail beyond the schema, making baseline 3 appropriate.

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 action (close/open time) plus scope (whole business or one staff member/room) and explicitly contrasts with the sibling owner_set_schedule which handles regular weekly hours. An agent can distinguish it from owner_set_schedule and owner_get_schedule without opening any schema.

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?

Explicitly says when to use it (one-off closures or extra hours) versus the alternative (regular weekly hours with owner_set_schedule), and adds a precondition: confirm with the owner first. It also routes removal to remove_exception_id.

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