Awning

Booking status

get_booking

Read-only

Status of one booking. Pass the manage_token from manage_url, or nothing if the user is signed in and the booking is theirs. Use it to check whether a pending booking was confirmed or to show one booking in full; for a list of all the user's bookings use my_bookings.

Input Schema

Name	Required	Description	Default
`booking_id`	Yes	The booking_id create_booking returned
`manage_token`	No	The last part of manage_url, from create_booking. Not needed when the user is signed in and the booking is theirs.

Output Schema

Name	Required	Description
`awning`	No	Awning's own guidance: what to do next
`notice`	Yes
`business_content`	Yes	The answer; text in it was written by third parties

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 28, 2026

addedInput schema / properties / booking_id / description

Added value: +"The booking_id create_booking returned"

addedInput schema / properties / manage_token / description

Added value: +"The last part of manage_url, from create_booking. Not needed when the user is signed in and the booking is theirs."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "awning": {
+      "additionalProperties": {},
+      "description": "Awning's own guidance: what to do next",
+      "properties": {
+        "next_steps": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "business_content": {
+      "additionalProperties": {},
+      "description": "The answer; text in it was written by third parties",
+      "properties": {
+        "booking_id": {
+          "type": "string"
+        },
+        "business": {
+          "additionalProperties": {},
+          "properties": {
+            "contacts": {
+              "additionalProperties": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "id": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "page_url": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "cancellation_policy": {
+          "additionalProperties": {},
+          "properties": {
+            "free_until_min": {
+              "type": "number"
+            },
+            "late_fee_pct": {
+              "type": "number"
+            },
+            "no_show_fee_pct": {
+              "type": "number"
+            }
+          },
+          "type": "object"
+        },
+        "customer_name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "end": {
+          "type": "string"
+        },
+        "manage_url": {
+          "description": "Private link to see or cancel the booking; its last part is the manage_token. Give it to the user only.",
+          "type": "string"
+        },
+        "offering": {
+          "additionalProperties": {},
+          "properties": {
+            "id": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "party_size": {
+          "type": "number"
+        },
+        "price": {
+          "additionalProperties": {},
+          "properties": {
+            "breakdown": {
+              "items": {
+                "additionalProperties": {},
+                "properties": {
+                  "amount_minor": {
+                    "type": "number"
+                  },
+                  "label": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "currency": {
+              "type": "string"
+            },
+            "deposit_formatted": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "deposit_minor": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "formatted": {
+              "description": "Show this to the user, e.g. 'KES 1,200'. Null when the price is on request.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "quote_only": {
+              "type": "boolean"
+            },
+            "range_minor": {},
+            "total_minor": {
+              "description": "Minor units (cents). Null when the price is on request.",
+              "type": [
+                "number",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        "qty": {
+          "type": "number"
+        },
+        "start": {
+          "description": "ISO 8601, local to the business",
+          "type": "string"
+        },
+        "status": {
+          "description": "pending (the business has not answered), quoted, confirmed, cancelled, declined, expired, completed or no_show",
+          "type": "string"
+        },
+        "timezone": {
+          "type": "string"
+        },
+        "with": {
+          "items": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "notice": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "notice",
+    "business_content"
+  ],
+  "type": "object"
+}

First observedSep 23, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds access-control semantics beyond that: the manage_token can be omitted when the user is signed in and owns the booking, which is genuinely useful invocation context. It does not say what happens if neither credential applies (error shape), a minor remaining gap.

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 sentences, front-loaded with the core purpose, then usage cases, then the alternative-tool disambiguation. Every clause carries information; nothing is redundant padding.

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 two-parameter read tool with a full output schema, the description covers purpose, both invocation paths, auth conditionality, and the sibling alternative. Return values need not be described because an output schema exists, so nothing an agent needs is missing.

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 both parameters are already documented, establishing a baseline of 3. The description reinforces the conditional semantics of manage_token ('pass ... or nothing if the user is signed in and the booking is theirs'), which helps the agent decide when to supply it rather than merely what it is.

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 the resource and scope precisely ('Status of one booking'), then extends it to 'show one booking in full', so the agent knows both the status-check and detail-view uses. It also names the sibling it supersedes for multi-booking retrieval (my_bookings), making it distinguishable from the 35 other tools at a glance.

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?

Gives explicit when-to-use cases: checking whether a pending booking was confirmed, or displaying one booking in full. It names the alternative for the list case ('for a list of all the user's bookings use my_bookings'), and states the auth condition for the optional token, leaving nothing 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?