Skip to main content
Glama

Export

export

Generate a raster PDF, vector PDF, or images ZIP and return a signed download URL.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish that this is a non-destructive, non-open-world operation, so the safety profile is covered. The description adds real value by disclosing the return shape (a signed download URL) and the three output formats, but says nothing about how long the signed URL lives, whether the export is long-running or expensive, or what permissions are required.

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?

One front-loaded sentence with a clear verb-object-result structure and zero wasted words. The outcome (signed download URL) is stated up front where an agent will read it first.

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

Completeness3/5

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

With no output schema, the description carries the burden of describing the return value, which it does adequately via the signed URL. However, for a tool with three distinct modes and three tuning parameters, it omits the bookId input entirely and gives no sense of latency, expiration, or failure behavior.

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 description coverage is already reported at 100%, so the baseline is 3. The description does add genuine meaning by mapping the op values to human-readable output types (pdf as raster, vector_pdf as vector, images_zip as an image archive), but it never mentions the vector-only tuning knobs (threshold, concurrency, forceRetrace) that materially change the result.

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 uses a specific verb plus three concrete output resources (raster PDF, vector PDF, images ZIP) and states that a signed download URL is returned, so the agent knows exactly what the call produces. It stops short of naming or contrasting any sibling tool, so an agent must still infer that this is the export step rather than the generate/book/pages tools.

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

Usage Guidelines2/5

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

There is no guidance on when to pick this tool over a sibling, no prerequisites (e.g. that a book must already exist), and no indication of which of the three modes to prefer for a given intent. The format list hints that multiple modes exist but leaves the choice entirely to the schema's op enum.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources