Chorus

Change the closing date, the questions and steps, or what people may send.

change_the_book

Idempotent

Changes the settings the organiser can change on the site: the day collecting stops, the questions people answer, whether they may send voice, video or writing, which one the button offers first, and whether the people recording are offered to chip in towards the printed book. Nobody is told about a change.

Input Schema

Name	Required	Description
`book`	Yes	The book’s handle.
`steps`	No	The whole list of steps, in order, in the shape a new book takes them. It replaces the steps the book had. An empty list goes back to plain questions. A person who already answered keeps their page.
`chip_in`	No	true offers everyone who records the chance to put money towards the printed book, which comes off what the organiser pays; false stops offering it.
`closes_on`	No	The day collecting stops, as a date. It means stop collecting rather than finished.
`lead_with`	No	Which one the big button offers first.
`questions`	No	The questions people answer, up to twelve.
`answer_with`	No	Any of voice, video and written.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 3, 2026

changedInput schema / properties / book / description

Previous value: -"The handle start_book gave you."New value: +"The book’s handle."

changedInput schema / properties / questions / description

Previous value: -"The questions people are asked, up to twelve."New value: +"The questions people answer, up to twelve."

changedInput schema / properties / steps / description

Previous value: -"The whole list of steps, in order, as start_book takes them. It replaces the steps the book had. An empty list goes back to plain questions. A person who already answered keeps their page."New value: +"The whole list of steps, in order, in the shape a new book takes them. It replaces the steps the book had. An empty list goes back to plain questions. A person who already answered keeps their page."

Changed1 schema field changedNov 3, 2026

addedInput schema / properties / steps

Added value: +{
+  "description": "The whole list of steps, in order, as start_book takes them. It replaces the steps the book had. An empty list goes back to plain questions. A person who already answered keeps their page.",
+  "items": {
+    "properties": {
+      "choices": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "kind": {
+        "enum": [
+          "words",
+          "song",
+          "photo",
+          "voice",
+          "date",
+          "choice",
+          "link",
+          "name"
+        ],
+        "type": "string"
+      },
+      "optional": {
+        "type": "boolean"
+      },
+      "text": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedNov 2, 2026

removedInput schema / properties / steps

Removed value: -{
-  "description": "The whole list of steps, in order, as start_book takes them. It replaces the steps the book had. An empty list goes back to plain questions. A person who already answered keeps their page.",
-  "items": {
-    "properties": {
-      "choices": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "kind": {
-        "enum": [
-          "words",
-          "song",
-          "photo",
-          "voice",
-          "date",
-          "choice",
-          "link",
-          "name"
-        ],
-        "type": "string"
-      },
-      "optional": {
-        "type": "boolean"
-      },
-      "text": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / steps

Added value: +{
+  "description": "The whole list of steps, in order, as start_book takes them. It replaces the steps the book had. An empty list goes back to plain questions. A person who already answered keeps their page.",
+  "items": {
+    "properties": {
+      "choices": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "kind": {
+        "enum": [
+          "words",
+          "song",
+          "photo",
+          "voice",
+          "date",
+          "choice",
+          "link",
+          "name"
+        ],
+        "type": "string"
+      },
+      "optional": {
+        "type": "boolean"
+      },
+      "text": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / chip_in

Added value: +{
+  "description": "true offers everyone who records the chance to put money towards the printed book, which comes off what the organiser pays; false stops offering it.",
+  "type": "boolean"
+}

AddedSep 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare mutation, idempotency, and non-destructiveness, so the description's key added value is 'Nobody is told about a change' — a genuine side-effect disclosure about notifications that no structured field carries. It does not clarify whether omitted fields are left untouched, which is the remaining behavioral 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?

A single front-loaded sentence that lists the affected settings efficiently, followed by a short side-effect note. No filler and no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter mutation tool with no output schema, the definition omits whether partial updates preserve existing values and who is permitted to call it, both of which affect correct invocation. The no-notification note and the enumerations cover much of the ground, but the update semantics gap keeps it at minimum-viable-plus.

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

Parameters3/5

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

Schema coverage is 100%, so all seven parameters are already documented, and the description's phrasing ('which one the button offers first', 'offered to chip in towards the printed book') largely restates those schema descriptions. The baseline 3 is appropriate; it adds nuance but no syntax or constraints beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Changes the settings') and enumerates the concrete settings affected: closing day, questions, allowed media, button order, and chip-in. It is clear what the tool mutates, though it does not explicitly separate itself from siblings like close_collecting or reopen_collecting that touch the same closing-date concept.

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

Usage Guidelines3/5

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

Usage is only implied through the enumerated settings; there is no statement of when to prefer this over close_collecting (for the closing date alone) or set_style. The agent must infer routing from the field list rather than being told.

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

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