Awning

Update business details

owner_update_business

DestructiveIdempotent

Only for business owners signed in to Awning. Change name, description, street address and its map point, public contacts, cancellation rules or automatic confirmation. Pass lat and lng with a new address when you know them; without them the old map point is dropped. A new name for a live business is reviewed by Awning first: customers keep seeing the current name until the team approves it, and the response says so under rename — tell the owner. Sending the current name again withdraws a new name that is waiting; a change of letter case only goes through at once. What is sent replaces what is there. Confirm with the owner first.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No
`lng`	No
`name`	No
`address`	No
`contacts`	No	Public contacts customers see: phone, whatsapp, telegram, instagram, website, email (public_email means the same as email). An empty string clears one; the ones not sent stay as they are.
`business_id`	No	Only needed if you manage several businesses
`description`	No
`auto_confirm`	No
`late_fee_pct`	No
`free_cancel_hours`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 29, 2026

addedInput schema / properties / address

Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}

changedInput schema / properties / contacts / additionalProperties
```
Previous value: -{
-  "type": "string"
-}New value: +false
```

addedInput schema / properties / contacts / description

Added value: +"Public contacts customers see: phone, whatsapp, telegram, instagram, website, email (public_email means the same as email). An empty string clears one; the ones not sent stay as they are."

addedInput schema / properties / contacts / properties

Added value: +{
+  "email": {
+    "maxLength": 200,
+    "type": "string"
+  },
+  "instagram": {
+    "maxLength": 200,
+    "type": "string"
+  },
+  "phone": {
+    "maxLength": 200,
+    "type": "string"
+  },
+  "public_email": {
+    "maxLength": 200,
+    "type": "string"
+  },
+  "telegram": {
+    "maxLength": 200,
+    "type": "string"
+  },
+  "website": {
+    "maxLength": 200,
+    "type": "string"
+  },
+  "whatsapp": {
+    "maxLength": 200,
+    "type": "string"
+  }
+}

removedInput schema / properties / contacts / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / properties / description / maxLength
```
Added value: +1000
```

addedInput schema / properties / lat

Added value: +{
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}

addedInput schema / properties / lng

Added value: +{
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}

addedInput schema / properties / name / maxLength
```
Added value: +120
```

First observedSep 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations declare idempotency and destructiveness, but the description adds substantial context the schema cannot: rename review workflow, customers seeing the old name until approval, the rename field in the response, that resending the current name withdraws a pending rename, that case-only changes apply immediately, and that the old map point is dropped when lat/lng are omitted. This is exactly the beyond-structured-data disclosure that earns top marks.

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?

Scope and the confirmation caution are front-loaded, and the dense rewrite/rename sentences each carry distinct operational facts. It is long but nearly every sentence earns its place; a little tightening of the rename sentences would make it ideal.

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?

For a 10-parameter mutation tool with no output schema and thin schema coverage, the description covers the critical behaviors (replace semantics, rename review, map-point drop, response signaling under rename). Remaining gaps are secondary: numeric semantics of late_fee_pct/free_cancel_hours and the rest of the response shape beyond rename.

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?

With only 20% schema description coverage the description must carry most semantic load, and it does: it explains lat/lng pairing with a new address, the rename behavior of the name field, the replace-everything semantics, and covers business_id, cancellation rules, and auto_confirm by name. It stops short of explaining formats/units for late_fee_pct and free_cancel_hours, keeping it out of 5 territory.

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+resource and enumerates exactly what can change: name, description, address and map point, public contacts, cancellation rules, and automatic confirmation. The opening 'Only for business owners signed in to Awning' immediately separates it from sibling tools like owner_update_offering or owner_set_schedule.

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

Usage Guidelines4/5

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

Gives a clear access precondition ('only for business owners signed in') and an operational instruction ('Confirm with the owner first'), plus when to pass lat/lng ('when you know them'). It does not name a competing sibling to route against, so it stops short of full when/when-not/alternative coverage.

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?