Chorus

Start a Chorus book, and get the one link to forward.

start_book

Starts a book of voice, video and written messages and returns the single link the organiser sends to everyone taking part. The book is for one person or a couple, or it is called by a title when it is for nobody in particular: a family’s recipes, a class’s year, a team’s goodbye. Start the simplest book that fits what the person said and hand over the link straight away. Gathering is free and the people recording need no app and no account. Use this as soon as somebody wants to collect messages from a group, whether or not there is an occasion. The first call emails the organiser a six digit code and makes nothing. Call it again with the same details and the code, and the book is made in their account.

Input Schema

TableJSON Schema

Name	Required	Description
`code`	No	The six digit code emailed to the organiser. Leave it out on the first call to have one sent.
`title`	No	What the book is called, in the person’s words, for example The Kelly family recipes. One line, up to 40 characters.
`occasion`	No	A big birthday, A wedding, A new baby, As they grow, In memory, or Something else. Plain words are matched to one of those.
`closes_on`	No	The day collecting stops, as 2026-11-14. Allow three weeks before the day if a printed copy is wanted.
`expecting`	No	Who is expected to record, by name or role, so book_status can say who is still out. Never email addresses.
`lead_with`	No	Which of those is the big button on a contributor’s phone.
`questions`	No	The questions everybody is asked, up to 12, written from what the person told you, each one line of up to 200 characters that a person can answer out loud in a minute or two. In a book with subject_name, {name} in a question becomes that name. When this is left out, a book with subject_name gets the set for the occasion and a book with only a title gets three open questions.
`answer_with`	No	Any of voice, video and written. Voice and written when not said.
`subject_name`	No	Who the book is for, when it is for one person or a couple, as the organiser says it, for example Mum. Give subject_name, title or both. A book for one person needs only subject_name.
`organiser_email`	Yes	The organiser’s email. The book belongs to this address and they get in with a six digit code.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 15, 2026

changedInput schema / properties / code / description

Previous value: -"The eight digit code emailed to the organiser. Leave it out on the first call to have one sent."New value: +"The six digit code emailed to the organiser. Leave it out on the first call to have one sent."

changedInput schema / properties / organiser_email / description

Previous value: -"The organiser’s email. The book belongs to this address and they get in with an eight digit code."New value: +"The organiser’s email. The book belongs to this address and they get in with a six digit code."

changedInput schema / properties / questions / description

Previous value: -"Questions to ask, if the organiser wants their own. The set for the occasion is used when this is left out."New value: +"The questions everybody is asked, up to 12, written from what the person told you, each one line of up to 200 characters that a person can answer out loud in a minute or two. In a book with subject_name, {name} in a question becomes that name. When this is left out, a book with subject_name gets the set for the occasion and a book with only a title gets three open questions."

changedInput schema / properties / subject_name / description

Previous value: -"Who the book is for, as the organiser says it, for example Mum."New value: +"Who the book is for, when it is for one person or a couple, as the organiser says it, for example Mum. Give subject_name, title or both. A book for one person needs only subject_name."

addedInput schema / properties / title

Added value: +{
+  "description": "What the book is called, in the person’s words, for example The Kelly family recipes. One line, up to 40 characters.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "subject_name",
-  "organiser_email"
-]New value: +[
+  "organiser_email"
+]

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / code / description

Previous value: -"The six digit code emailed to the organiser. Leave it out on the first call to have one sent."New value: +"The eight digit code emailed to the organiser. Leave it out on the first call to have one sent."

changedInput schema / properties / organiser_email / description

Previous value: -"The organiser’s email. The book belongs to this address and they get in with a six digit code."New value: +"The organiser’s email. The book belongs to this address and they get in with an eight digit code."

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / code

Added value: +{
+  "description": "The six digit code emailed to the organiser. Leave it out on the first call to have one sent.",
+  "type": "string"
+}

First observedSep 7, 2026

TDQS

A4.2/5.0

Behavior5/5

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

With annotations only declaring readOnly=false and idempotent=false, the description carries real extra load: it discloses the two-step flow (first call emails a six-digit code and creates nothing, second call with the same details plus code creates the book) and that gathering is free with no app or account needed by contributors. This is behavioral context an agent cannot get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence front-loads purpose well, but the middle section drifts into examples of occasion types and 'the Kelly family' imagery that add length without invocation-relevant detail. Several sentences could be trimmed without losing guidance.

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 creation tool with no output schema, the description covers what is produced (a link) and the two-call code flow, which is the critical thing an agent needs. It does not address error or failure behavior, but nothing essential for correct invocation is missing.

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 description coverage is 100% and every parameter already has a rich description, so the schema does the heavy lifting. The prose confirms the title/subject_name relationship and the code flow but adds little syntax or format detail beyond what the schema already states. Baseline 3 is appropriate.

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 — starting a book of voice, video and written messages — and explicitly says it returns the single link the organiser forwards. An agent can tell this apart from change_the_book or book_status without opening the schema.

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 strong when-to-use guidance: 'Use this as soon as somebody wants to collect messages from a group, whether or not there is an occasion' and 'Start the simplest book that fits what the person said.' It does not name a sibling alternative or exclusion, which keeps it short of a 5.

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?