book_statusReturns who is in with their name and relationship, how many voices, videos and written messages have landed, how many carried a photo, who the organiser is still waiting on, and the days left before collecting stops.
| Name | Required | Description | Default |
|---|---|---|---|
| book | Yes | The handle start_book gave you. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds detail about the returned status fields but no additional behavioral traits such as side effects, permissions, or rate limits, which is acceptable given the annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that starts with the action and then efficiently lists all status elements. Every clause adds useful information, with no filler or repetition of schema details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Even without an output schema, the description fully explains what the agent should expect: names and relationships, counts by media type, photo count, outstanding people, and days remaining. For a simple status query with one parameter, this is complete enough to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for the single 'book' parameter, explaining it as the handle start_book gave. The tool description adds no extra parameter meaning, but because the schema already documents the parameter fully, the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a clear verb ('Returns') and a specific resource (book collection status), then enumerates exactly what status information is provided: who is in, message counts, photo counts, missing people, and days left. This clearly distinguishes it from siblings like order_status and start_book.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context is clear: this tool reports collection progress, including outstanding contributors and time remaining. It does not explicitly name alternatives or state when not to use it, but its purpose is distinct enough among the sibling tools that an agent can infer when to call it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.