SimpleDock

This connector has been deprecated

Duplicate listing. This is the same server as SimpleDock (ai.simpledock/simple-dock) (https://simpledock.ai/api/v1/mcp). Please use that listing instead.

Update booking question

update_booking_question

DestructiveIdempotent

Edit a booking question (Pro). Omitted fields are left unchanged; the key never changes. isActive: false hides it from the form but keeps past answers (prefer this to delete_booking_question). Returns the updated question. Requires scope locations:write (Admin role).

Input Schema

Name	Required	Description
`label`	No	Question shown to carriers.
`options`	No	Choices for DROPDOWN; replaces the whole list.
`helpText`	No	Hint shown under the question.
`isActive`	No	false = hidden from the form, answers kept.
`required`	No	Must be answered to book.
`fieldType`	No	Answer input type. MULTI_TEXT holds a list, such as several PO numbers.
`locationId`	Yes	Location id, from list_locations.
`questionId`	Yes	Booking question id, from list_booking_questions.
`isReference`	No	Treat the answer as a searchable reference number.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / fieldType / description

Previous value: -"Answer input type."New value: +"Answer input type. MULTI_TEXT holds a list, such as several PO numbers."

changedInput schema / properties / fieldType / enum

Previous value: -[
-  "SHORT_TEXT",
-  "LONG_TEXT",
-  "NUMBER",
-  "DROPDOWN",
-  "BOOLEAN",
-  "DATE"
-]New value: +[
+  "SHORT_TEXT",
+  "LONG_TEXT",
+  "NUMBER",
+  "DROPDOWN",
+  "BOOLEAN",
+  "DATE",
+  "MULTI_TEXT"
+]

Changed9 schema fields changedOct 16, 2026
- addedInput schema / properties / fieldType / description
```
Added value: +"Answer input type."
```
- addedInput schema / properties / helpText / description
```
Added value: +"Hint shown under the question."
```
- addedInput schema / properties / isActive / description
```
Added value: +"false = hidden from the form, answers kept."
```
- addedInput schema / properties / isReference / description
```
Added value: +"Treat the answer as a searchable reference number."
```
- addedInput schema / properties / label / description
```
Added value: +"Question shown to carriers."
```
- addedInput schema / properties / locationId / description
```
Added value: +"Location id, from list_locations."
```
- addedInput schema / properties / options / description
```
Added value: +"Choices for DROPDOWN; replaces the whole list."
```
- addedInput schema / properties / questionId / description
```
Added value: +"Booking question id, from list_booking_questions."
```
- addedInput schema / properties / required / description
```
Added value: +"Must be answered to book."
```
First observedOct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true) by disclosing partial-update semantics ("Omitted fields are left unchanged"), immutability of the identifier, the soft-disable behaviour versus deletion, the return value, and the auth scope required. That is exactly the extra context annotations cannot carry.

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?

Four short sentences, front-loaded with the verb and resource, then the update contract, then the isActive-versus-delete guidance, then the return and auth requirements. No sentence is redundant.

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 nine-parameter mutation with no output schema, it covers the mutation contract, the destructive-alternative decision, the return shape ("Returns the updated question"), and the permission requirement. An agent has everything needed to decide and call correctly.

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 per-parameter meaning is already documented and the baseline is 3. The description adds genuine semantics beyond the schema by clarifying the PATCH contract for all nine parameters and stating questionId is immutable, which the schema does not say.

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 ("Edit a booking question") and flags the Pro tier constraint, which lets an agent separate it from create_booking_question and delete_booking_question in the sibling list. The added note that the key never changes pins down the exact scope of the edit.

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?

Explicitly routes the agent away from a sibling: "prefer this to delete_booking_question" with the condition (isActive: false keeps past answers). It also names the prerequisite (scope locations:write, Admin role), so the agent knows before calling whether it is eligible.

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

All SimpleDock 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?