Skip to main content
Glama
Sign In

Awning

by help.awning
OverviewDiscussionsAdmin

Class timetable

owner_upsert_sessions
DestructiveIdempotent

Only for business owners signed in to Awning. Set when a class runs; future classes are generated for the booking horizon. Use it for a class (sessions-mode offering) whose weekly timetable changes; the timetable sent replaces the class's old weekly pattern, so send all of it; classes already generated are kept. Not for appointments or rentals (owner_set_schedule sets their hours).

Input Schema

NameRequiredDescriptionDefault
scheduleYesThe weekly timetable: each entry is a day pattern and a start time
business_idNoWhich business, when the owner runs several: business_id from owner_status. Leave out when there is only one.
offering_idYesThe class: offerings[].offering_id of a sessions-mode offering

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 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 / offering_id / description
      Added value: +"The class: offerings[].offering_id of a sessions-mode offering"
    • addedInput schema / properties / schedule / description
      Added value: +"The weekly timetable: each entry is a day pattern and a start time"
    • addedInput schema / properties / schedule / items / properties / capacity / description
      Added value: +"Seats in total"
    • addedInput schema / properties / schedule / items / properties / capacity_online / description
      Added value: +"Seats that can be booked online"
    • changedInput schema / properties / schedule / 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 / schedule / items / properties / days / description
      Removed value: -"e.g. \"mon-sat\", \"daily\", [\"tue\",\"thu\"]"
    • addedInput schema / properties / schedule / items / properties / duration_min / description
      Added value: +"Length in minutes"
    • addedInput schema / properties / schedule / items / properties / time / description
      Added value: +"Start time, 24-hour HH:MM"
    • removedInput schema / properties / schedule / items / properties / time / maxLength
      Removed value: -20
  2. Changed3 schema fields changed
    • changedInput schema / properties / schedule / 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 / schedule / items / properties / time / maxLength
      Added value: +20
    • addedInput schema / properties / schedule / maxItems
      Added value: +50
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations say destructiveHint=true and idempotentHint=true, but the description earns its keep by explaining the mechanics: the submitted timetable replaces the old weekly pattern wholesale, and already-generated classes survive. That replacement semantics is exactly the destructive behavior an agent needs to understand before calling.

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?

Dense and largely front-loaded, with the replacement caveat and the sibling exclusion stated early. The auth precondition leads ahead of the core purpose, which slightly delays the key verb, but no sentence is 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?

A destructive mutation with no output schema and no annotation detail on returns is adequately covered: replacement behavior, retention of generated classes, and the correct alternative are all present. Return shape and what happens on invalid day patterns are unstated, a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds real semantic weight to the schedule parameter by saying the full timetable must be sent because it replaces the prior pattern. The offering_id/business_id meaning is left to the schema, so it stops short of a 5.

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 verb and resource ("Set when a class runs") and immediately scopes it to sessions-mode offerings whose weekly timetable changes. It explicitly separates itself from owner_set_schedule, which covers appointments and rentals, so an agent can route correctly without reading 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?

Names the precondition (business owners signed in, sessions-mode class), the trigger condition (weekly timetable changes), and the explicit exclusion with the alternative tool named ("Not for appointments or rentals (owner_set_schedule sets their hours)"). When-to-use and when-not-to-use are both stated.

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