Skip to main content
Glama
Sign In

EasyAccessPDF

by io.github.luotwo
OverviewDiscussionsAdmin

eap_convert_to_markdown

Read-onlyIdempotent

Convert a document to clean Markdown (included with membership, no credits). Formats: PDF, Word (.docx/.doc), PowerPoint, Excel, HTML, EPUB, RTF, ODT, TXT. Pass a publicly accessible URL of the document.

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": {
      "url": "<url>"
    },
    "name": "eap_convert_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublicly accessible URL of the document (max 50MB)

Output Schema

NameRequiredDescriptionDefault
markdownYesThe converted document as clean Markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds genuinely new context: the conversion is 'included with membership, no credits,' which tells the agent there is no billing cost or credit consumption, and 'clean Markdown' signals output quality. It does not mention processing latency, failure modes on unsupported or inaccessible URLs, or that the URL is fetched externally, but those are secondary given the annotations.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core operation, then the format list, then the input requirement. No filler, no repetition of the title, and every clause carries information an agent can act on.

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?

For a one-parameter, read-only conversion tool with an output schema already describing the return value, the description covers operation, supported formats, input requirement, and cost model. Nothing an agent needs in order to call it correctly 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?

There is a single parameter with 100% schema description coverage, so the schema already documents the URL and its 50MB limit. The description merely restates 'pass a publicly accessible URL of the document' without adding syntax, auth, or edge-case meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 ('Convert a document to clean Markdown') and enumerates the accepted input formats (PDF, Word, PowerPoint, Excel, HTML, EPUB, RTF, ODT, TXT), which cleanly separates it from the sibling PDF-utility tools (check/export/fix) and account-status tool. An agent can identify the operation and its input universe without opening 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 Guidelines3/5

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

The description implies usage through the format list and the instruction to pass a publicly accessible URL, but it never states when to prefer this tool over a sibling or when it is the wrong choice (e.g., PDF-only manipulation). Guidance is inferable rather than explicit, and no exclusions or alternatives are named.

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

All EasyAccessPDF 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