Skip to main content
Glama
Sign In

Epublys

by com.epublys
OverviewDiscussionsAdmin

upgrade_to_pro

Get a checkout link so the user can upgrade THIS account to Epublys Pro.

Call this when another tool is refused with daily_limited or a Pro-only error, or when the user asks to upgrade. Returns a Stripe checkout URL to hand to the user — they complete payment in their own browser.

Creates no charge by itself, and the link is bound to the account that owns the API key being used, so it cannot be used to pay for anyone else. If the account is already Pro it says so and returns no link. Needs an API key: without one it returns the pricing URL instead of a checkout link. Free: 3 operations/day, 5MB per file. Pro: unlimited daily operations, 30MB per operation, 60 req/min, no branding on output.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upgrade_to_pro"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNomonthly is $9/month; yearly is $72/year (4 months free, 33% off). Defaults to monthly.monthly

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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: no charge is created, the link is bound to the calling account's key and cannot pay for others, already-Pro accounts get a message rather than a link, and a missing API key yields a pricing URL. These are exactly the non-obvious behaviors an agent needs before calling a payment-adjacent tool.

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 important material is front-loaded: purpose, then trigger conditions, then edge cases. The closing Free-vs-Pro tier list is a marketing restatement that is only marginally useful for tool selection and could be trimmed.

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?

Return values are described in both branches (checkout URL vs pricing URL vs already-Pro message), preconditions are stated, and the account binding is clarified. For a one-param tool with no output schema, nothing an agent needs 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% and the single `plan` param already documents pricing and the monthly default, so the description needn't repeat it. It adds nothing about the parameter, leaving it at the baseline.

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 and resource ('Get a checkout link') and pins the scope with 'THIS account ... Epublys Pro'. It is unmistakably distinct from every sibling, which are all EPUB/PDF conversion and metadata utilities.

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

Usage Guidelines5/5

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

Gives explicit triggers: when another tool is refused with `daily_limited` or a Pro-only error, or when the user asks to upgrade. It also names the branch conditions that change behavior (already Pro, missing API key), so the agent knows when not to expect a link.

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