Skip to main content
Glama
Sign In

Epublys

by com.epublys
OverviewDiscussionsAdmin

read_epub_metadata

Read metadata from an EPUB file (title, author, language, publisher, description, series, cover status, etc.). Returns JSON — no file output.

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": "read_epub_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesBase64-encoded EPUB file content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 disclose important behavior: JSON output, no file output, free-tier and Pro size/rate limits, branding differences, and the upgrade path on daily_limited or Pro-only errors. It does not explicitly state read-only safety or side-effect behavior, but the operation is clearly framed as a read.

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 description is front-loaded with the core purpose and output behavior, followed by concise plan limits and upgrade routing. The pricing details are somewhat verbose but relevant to the documented error-handling path.

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 one-parameter read tool with no output schema, the description is mostly complete: it names the metadata fields returned, states the JSON/no-file output behavior, and documents size/rate limits plus the upgrade path. Exact return schema details are not provided, but the description is sufficient for an agent to call it correctly.

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?

There is one required parameter, and schema description coverage is 100%, so the schema already explains that 'file' is base64-encoded EPUB content. The description adds little parameter-specific meaning beyond reinforcing that an EPUB file is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: read metadata from an EPUB file. It lists the kinds of metadata returned and clarifies that the result is JSON with no file output. It does not explicitly contrast with the sibling edit_epub_metadata tool, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The core use case is implied by 'Read metadata,' and the description explicitly routes refused calls to upgrade_to_pro. However, it does not say when to use this instead of validate_epub or edit_epub_metadata, so usage guidance remains partial.

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