PDFInvoiceAPI
Server Details
Turn HTML or templates into branded invoice & document PDFs from your agent. One call, no install.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 1 of 1 tools scored.
Only one tool exists, so there is no ambiguity in tool selection.
The single tool follows a clear verb_noun pattern (render_pdf), consistent within the set.
A single tool is too few for a PDF service; typical workflows require template management, listing, or other operations.
The tool handles rendering but lacks other essential operations like template creation, updating, or deleting, leaving significant gaps for a full PDF API.
Available Tools
1 toolrender_pdfRender PDFAInspect
Render a professional PDF (invoice/receipt/contract/document) from inline html or a stored template + data, and return the PDF. Provide exactly one of html or template. Supports paper format, orientation, margins and scale. Requires an API key (Authorization: Bearer) — get one at https://pdfinvoiceapi.com.
| Name | Required | Description | Default |
|---|---|---|---|
| No | Optional page options passed to the PDF engine. | ||
| data | No | Key/value data merged into `template` ({{placeholders}}). Ignored with `html`. | |
| html | No | Inline HTML to render to a PDF. Provide EXACTLY ONE of `html` or `template`. | |
| template | No | Either a stored template id (e.g. "tpl_invoice") OR an inline template string with {{placeholders}}, merged with `data`. Provide EXACTLY ONE of `html` or `template`. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description must fully disclose behavior. It describes the core function, supported features (format, orientation, margins, scale), and authentication. It does not mention rate limits, error cases, or idempotency, which is acceptable for a creation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each serving a purpose: stating the action, providing the constraint, and listing features/auth. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers all essential aspects for a tool with no output schema: purpose, input choices, configuration options, and authentication. Could mention the return type more explicitly, but 'return the PDF' is sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but the description adds significant meaning: explains the mutual exclusivity of 'html' and 'template', clarifies that 'template' can be an ID or inline string, and that 'data' is only used with 'template'. This goes well beyond the schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'render' and the resource 'professional PDF', and specifies the two input modalities (inline HTML or stored template + data). No sibling tools exist, so differentiation is irrelevant.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit instruction to provide exactly one of 'html' or 'template'. Also mentions API key requirement. However, no guidance on when to choose this tool over alternatives or exclusions, but siblings are absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!