Awning

Set working hours

owner_set_schedule

DestructiveIdempotent

Only for business owners signed in to Awning. Replace weekly hours of the business, or of one staff member/room with resource_id. Existing bookings are kept. Use it for the regular weekly pattern; for a one-off day off or extra hours use owner_block_time. The hours sent replace all the old ones, so send the whole week.

Input Schema

Name	Required	Description
`hours`	Yes	Local, 24-hour: [{"days":"mon-sat","open":"09:00","close":"18:00"}]; days also "daily", ["tue","thu"]; a break is two ranges
`business_id`	No	Which business, when the owner runs several: business_id from owner_status. Leave out when there is only one.
`resource_id`	No	Only this staff member, room or rental pool: an id from owner_get_schedule. Leave out for the whole business.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 28, 2026

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 / hours / description

Added value: +"Local, 24-hour: [{\"days\":\"mon-sat\",\"open\":\"09:00\",\"close\":\"18:00\"}]; days also \"daily\", [\"tue\",\"thu\"]; a break is two ranges"

removedInput schema / properties / hours / items / properties / close / description
```
Removed value: -"HH:MM"
```
removedInput schema / properties / hours / items / properties / close / maxLength
```
Removed value: -20
```

changedInput schema / properties / hours / items / properties / days / anyOf

Previous value: -[
-  {
-    "maxLength": 100,
-    "type": "string"
-  },
-  {
-    "items": {
-      "maxLength": 20,
-      "type": "string"
-    },
-    "maxItems": 14,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / hours / items / properties / days / description
```
Removed value: -"e.g. \"mon-sat\", \"daily\", [\"tue\",\"thu\"]"
```
removedInput schema / properties / hours / items / properties / open / description
```
Removed value: -"HH:MM"
```
removedInput schema / properties / hours / items / properties / open / maxLength
```
Removed value: -20
```
removedInput schema / properties / hours / maxItems
```
Removed value: -100
```

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."

Changed4 schema fields changedSep 29, 2026

addedInput schema / properties / hours / items / properties / close / maxLength
```
Added value: +20
```

changedInput schema / properties / hours / items / properties / days / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "maxLength": 100,
+    "type": "string"
+  },
+  {
+    "items": {
+      "maxLength": 20,
+      "type": "string"
+    },
+    "maxItems": 14,
+    "type": "array"
+  }
+]

addedInput schema / properties / hours / items / properties / open / maxLength
```
Added value: +20
```
addedInput schema / properties / hours / maxItems
```
Added value: +100
```

First observedSep 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The annotations only say destructive=true and idempotent=true; the description adds the crucial detail of what is actually destroyed — old hours are fully replaced while existing bookings are kept — plus the owner-only auth precondition. That is exactly the context an agent needs before committing a destructive write.

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?

Five short sentences, front-loaded with the audience gate and the core replace semantics, then the alternative and the whole-week warning. Zero filler.

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?

Auth, replacement semantics, booking preservation and the sibling alternative are all covered, which is nearly everything an agent needs for a destructive write. There is no output schema, and the description never says what comes back or how invalid/overlapping ranges are handled — a minor remaining gap.

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%: hours format, business_id provenance and resource_id source are all documented in the schema. The description only gestures at resource_id scoping, so it adds little beyond the structured fields. A 3 baseline is appropriate here.

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 verb (replace) and resource (weekly hours), and scopes it to the whole business or one resource via resource_id. It explicitly contrasts with owner_block_time, so an agent can pick the right tool without opening either 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?

It gives an explicit audience gate (business owners signed in to Awning), an explicit when (regular weekly pattern), and an explicit when-not with the alternative named (one-off day off or extra hours → owner_block_time). Nothing is left to inference.

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

All Awning tools Inspect

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

Need Help?