Skip to main content
Glama

Chorus

by com.choruskeepsake

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

start_book

Starts a book of voice, video and written messages for one person, and returns the single link the organiser sends to everyone taking part. 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 for one person, whether or not there is an occasion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
occasionNoA big birthday, A wedding, A new baby, As they grow, In memory, or Something else. Plain words are matched to one of those.
closes_onNoThe day collecting stops, as 2026-11-14. Allow three weeks before the day if a printed copy is wanted.
expectingNoWho is expected to record, by name or role, so book_status can say who is still out. Never email addresses.
lead_withNoWhich of those is the big button on a contributor’s phone.
questionsNoQuestions to ask, if the organiser wants their own. The set for the occasion is used when this is left out.
answer_withNoAny of voice, video and written. Voice and written when not said.
subject_nameYesWho the book is for, as the organiser says it, for example Mum.
organiser_emailYesThe 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. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations are all false and provide no safety or idempotency signals, so the description carries the burden. It adds meaningful behavioral context: gathering is free, contributors need no app and no account, and the tool returns a single forwardable link. It does not mention side effects like persistent storage or later management via siblings, but the core behavior is transparent enough for invocation.

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 sentences with no wasted words. The main function and output are front-loaded, followed by key user-facing benefits and a clear usage trigger. Every sentence contributes to the agent's ability to decide when and why to call the tool.

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 tool with 8 parameters and no output schema, the description is nearly complete: it states the purpose, the trigger condition, the key returned artifact, and a major constraint about contributors needing no account. It could mention that the book belongs to the organiser email, but that is already captured in the organiser_email parameter description.

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%, so the schema already documents all eight parameters in detail. The description adds overall context — one recipient, group contributors, a single link — but does not add per-parameter meaning beyond the schema. 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?

The description uses a specific verb and resource: 'Starts a book of voice, video and written messages for one person, and returns the single link the organiser sends to everyone taking part.' It clearly identifies the tool's core action and output, and differentiates it from siblings like get_links by emphasizing that this creates the book and returns the one link to forward.

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?

The description explicitly states when to use the tool: 'Use this as soon as somebody wants to collect messages from a group for one person, whether or not there is an occasion.' This gives a clear triggering condition, and the phrase 'whether or not there is an occasion' prevents the agent from requiring an occasion to exist.

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

All Chorus toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool clearly targets a distinct part of the book lifecycle: starting, collecting, closing, reopening, sharing links, and checking collection or order status. There is no meaningful overlap or ambiguity between the tools.

Naming Consistency3/5

Most tools follow a verb_noun pattern like start_book, close_collecting, and get_links, while book_status and order_status use a noun_status pattern. The bare 'order' tool breaks the pattern and could be seen as a noun or verb, making the naming slightly mixed but still readable.

Tool Count5/5

Seven tools is well-scoped for the server's purpose: managing a message-collection book from creation through ordering. Each tool covers a necessary lifecycle step with no obvious redundancy.

Completeness4/5

The core lifecycle of starting, sharing, monitoring, closing, reopening, and ordering is well covered. Minor gaps exist around modifying or cancelling orders and retrieving pricing, but these are partially addressed through external links and the provided pricing URL.

Resources