Skip to main content
Glama
Sign In

Ignix

by social.ignix
OverviewDiscussionsAdmin

Edit a person or room for bookings

update_booking_resource
DestructiveIdempotent

Change a person or room (resourceId from get_booking_settings); only what you pass changes. hours and timeOff are replaced as a whole: read the current ones in get_booking_settings first. active false stops it being booked without deleting it.

Input Schema

NameRequiredDescriptionDefault
nameNoUp to 80 characters, e.g. "Ana" or "Room 2".
hoursNoWeekly hours: {"mon": [["09:00","14:00"],["16:00","20:00"]], "tue": [...], ...}. Days mon…sun; a missing day is closed.
spotsNoCustomers at the same time, 1-500. Default 1. For a restaurant table type: how many tables of that type.
activeNofalse stops it from being booked without deleting it.
timeOffNoWhole days off, both inclusive. Replaces the current list.
partyMaxNoRestaurant table type only: most people it seats. null = no limit.
partyMinNoRestaurant table type only: fewest people it seats. Default 1.
resourceIdYesThe person or room, from get_booking_settings.
workspaceIdNoDefaults to the workspace this connection is scoped to.
idempotencyKeyNoOptional. A unique id for this action (16-128 chars: letters, digits, _ : . -). If you are unsure whether a call went through (timeout, network error), repeat it with the SAME idempotencyKey and the same arguments: you get the original result and nothing is done twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / partyMax
      Added value: +{
+  "description": "Restaurant table type only: most people it seats. null = no limit.",
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedInput schema / properties / partyMin
      Added value: +{
+  "description": "Restaurant table type only: fewest people it seats. Default 1.",
+  "type": "number"
+}
    • changedInput schema / properties / spots / description
      Previous value: -"Customers at the same time, 1-500. Default 1."New value: +"Customers at the same time, 1-500. Default 1. For a restaurant table type: how many tables of that type."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare this destructive, idempotent, and non-read-only; the description adds the specific destructive mechanism (hours and timeOff are replaced wholesale, so read current values first) and the non-destructive disable path via active=false. That is exactly the context an agent needs before calling a destructive update.

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?

Three dense sentences, front-loaded with the action and scope, then the dangerous replacement semantics, then the disable option. 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?

For a 10-parameter nested mutation tool with no output schema, the description covers the risky semantics and the identity source. It does not say what comes back after a successful update, though the idempotencyKey schema text implies the original result is returned.

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 earns an extra point by adding semantics the schema does not: PATCH-style partial update ("only what you pass changes") and whole-replacement behavior for hours and timeOff. Minor parameters (spots, partyMax/Min, workspaceId) get no mention, but the schema documents them.

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?

A specific verb ("change") applied to a specific resource ("a person or room"), with the identity source named (resourceId from get_booking_settings). This separates it cleanly from create_booking_resource, delete_booking_resource, and update_booking_settings/update_booking_service.

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?

States the prerequisite read (get_booking_settings) before replacing hours/timeOff, and explains that active=false is the soft alternative to deletion. It never explicitly says when not to use it versus update_booking_settings, but the resource-level framing does the routing work.

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

All Ignix 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