Skip to main content
Glama
Sign In

Epublys

by com.epublys
OverviewDiscussionsAdmin

split_epub

Split an EPUB. With a chapter range (chapterStart and/or chapterEnd) the result is ONE base64-encoded EPUB of exactly those chapters, in order, with the book's metadata, a table of contents limited to them and the fonts and images they use. Without a range the result is a base64-encoded ZIP archive holding one EPUB per chapter.

Free tier: 5MB/file (10MB for pdf-to-epub, 15MB for split), 3 operations/day, 15 req/min, output includes Epublys branding. Pro ($9/mo): 30MB per operation, unlimited daily operations, 60 req/min, no branding.

When a call is refused with daily_limited or a Pro-only error, call the upgrade_to_pro tool — it returns a checkout link to hand the user. Details: https://epublys.com/pricing

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "<file>"
    },
    "name": "split_epub"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesBase64-encoded EPUB file content
nameNoOriginal filename — the output is named after its stem (e.g. "Book.epub" gives "Book (compressed).epub"); without it the output keeps a fixed name
chapterEndNoLast chapter to include (inclusive, optional)
chapterStartNoFirst chapter to include (1-indexed, optional). Giving either bound returns one EPUB of the range instead of a ZIP
keepMetadataNoPreserve the original author, publisher and description in the output

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses output encoding, metadata preservation, TOC scoping, retained fonts/images, plus concrete rate limits (3 ops/day, 15 req/min), size caps, branding behavior, and the error-triggered upgrade path. This is unusually rich behavioral context.

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

Conciseness4/5

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

The core split behavior and two output modes are front-loaded in the first sentence, followed by pricing/limits. The tier block is somewhat long but each line carries actionable constraint information an agent needs for error handling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description fully explains what is returned in both modes and covers limits and recovery paths. 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 coverage is 100%, so the schema already documents all five parameters thoroughly, including the 1-indexed range and mode-switch behavior. The description reinforces the range semantics but adds no new per-parameter detail, so the 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 (Split) and resource (EPUB), and precisely describes the two distinct output shapes: a single base64 EPUB for a chapter range versus a base64 ZIP of per-chapter EPUBs. An agent can distinguish this from siblings like merge_epub or compress_epub without inspecting 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?

Clearly explains the mode selection rule: supplying chapterStart/chapterEnd yields one ranged EPUB, omitting them yields a ZIP. It also routes the agent to `upgrade_to_pro` on daily_limited or Pro-only errors. It does not, however, contrast this tool against sibling alternatives such as merge_epub or compress_epub.

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

All Epublys toolsInspect
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