Upload a version of a book you authored. The content is stored as Markdown and becomes the new HEAD.
| Name | Required | Description | Default |
|---|---|---|---|
| book_id | Yes | ||
| content | Yes | Full Markdown content of the book | |
| preview | No | Optional preview text. Defaults to first 30% of content. | |
| version | Yes | Semver, e.g. '1.0.0' | |
| changelog | No |
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?
With no annotations, the description carries the transparency burden. It discloses key behavioral traits: content is stored as Markdown and becomes the new HEAD, which implies replacement/overwrite semantics. It also implicitly requires authorship. It does not mention reversibility, errors, or return behavior, but the essential behavior is disclosed.
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?
A single, front-loaded sentence that conveys purpose, ownership, storage format, and versioning effect. No wasted words.
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?
Given there are 5 parameters, no annotations, and no output schema, the description covers core purpose and effects but omits return values, error cases, permissions (beyond authorship), and specifics for two parameters. It is viable but incomplete for a full agent-facing contract.
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?
Schema coverage is 60% with descriptions for content, preview, and version. The description adds semantic weight to content ('stored as Markdown', 'becomes new HEAD') but does not clarify book_id or changelog. This is adequate but not a full compensation for uncovered parameters.
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 specific verb ('Upload') and resource ('version of a book you authored'), clearly distinguishing this from sibling tools like post_book or update_book via the versioning and 'new HEAD' semantics.
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 phrase 'a book you authored' gives clear contextual guidance for when the tool should be used, implying an ownership prerequisite. However, it does not explicitly state when not to use it or name alternatives among siblings.
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.
Several tools have overlapping purposes. For example, list_my_books and my_books both list authored books, and author_dashboard is a superset; list_orders and my_orders are near-duplicates; check_earnings and payout_balance both report earnings. This creates confusion and risks misselection.
Naming is inconsistent. While many tools use verb_noun (list_annotations, get_book_details), others use my_* (my_books, my_orders), bare nouns (payout_balance), or compound verbs (connect_onboard). The lack of a uniform pattern makes the set feel disjointed.
49 tools is excessive for a server, especially with at least three sets of near-duplicates. The platform is complex, but many tools could be merged (e.g., my_books and list_my_books, list_orders and my_orders). This count will overwhelm agents and increase misselection risk.
The toolset covers the core domain well: discover, purchase, read, comment, review, annotate, publish, monetize, verify, and manage payouts. Minor gaps exist, such as no update/delete annotation, no delete review, and no single-item getter for annotations/reviews, but these are not critical to the main workflows.