order_statusReturns whether the book has been paid for and which option was bought, and on a printed one the stage the printer is at with the tracking.
| 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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds context about what data is returned (payment status, option, printing stage), which is useful beyond annotations. It does not disclose any other behavioral traits like auth or rate limits, but given the annotations, a 3 is appropriate.
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 long sentence that is somewhat convoluted, especially the clause 'on a printed one the stage the printer is at with the tracking.' It could be split and reworded for clarity, but it is not excessively long. It front-loads the main purpose but the phrasing detracts from conciseness.
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?
There is no output schema, so the description must explain return values. It partially does (payment status, option, printing stage), but it is ambiguous about what 'on a printed one' means and what 'tracking' refers to. It also doesn't specify the format of the returned data. For a simple status check, this is insufficient for an agent to reliably parse the output.
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 only parameter 'book' is fully described in the schema ('The handle start_book gave you'), and the description does not add any additional meaning. Since schema coverage is 100%, the baseline of 3 is justified.
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 clearly states the tool returns payment status, purchased option, and printing stage for a book. It uses a specific verb ('returns') and resource ('book'), distinguishing it from sibling tools like 'order' (placing orders) and 'book_status' (likely different status). However, the phrase 'on a printed one' is ambiguous, slightly weakening clarity.
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 description provides no guidance on when to use this tool versus alternatives such as 'book_status' or 'order'. It does not mention prerequisites (e.g., needing a handle from start_book) or exclude scenarios. An agent must infer usage from the tool name alone.
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.