html_to_pdf
Convierte HTML a PDF. Retorna base64. Cuesta 5 créditos.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| html | Yes | HTML completo a convertir | |
| options | No | Opciones: landscape, margin |
mifactory-pdf
TDQS
A3.8/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. It discloses the base64 return format and the 5-credit cost, which are important behavioral traits. It stops short of explaining side effects or failure modes, but for a conversion tool these are less critical.
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?
The description is extremely concise and front-loaded with the action. Every word earns its place, covering purpose, output, and cost without any fluff.
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 simple tool with 2 parameters and no output schema, the description covers the essentials: purpose, return format, and cost. It does not elaborate on options specifics, but the schema covers that. Overall, it is adequately complete.
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%, so the baseline is 3. The description adds no extra meaning about the parameters beyond what the schema already provides for 'html' and 'options'.
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?
The description 'Convierte HTML a PDF' uses a specific verb (convierte) and resource (HTML a PDF), clearly distinguishing it from sibling tools like markdown_to_pdf. The purpose is immediately evident.
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?
No guidance is provided on when to use this tool versus alternatives. It simply states what it does without mentioning any use cases, exclusions, or comparisons to sibling tools.
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.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool has a distinct purpose: HTML to PDF, Markdown to PDF, invoice generation, and report generation. No two tools overlap in function, so an agent can clearly select the right tool based on input format or document type.
Naming Consistency4/5
All tool names use lowercase with underscores and end with '_pdf'. While there are two patterns ('X_to_pdf' and 'X_pdf'), they are both clear and follow a predictable structure, so the overall convention is consistent.
Tool Count5/5
With 4 tools, the set is well-scoped for a PDF generation server. Each tool covers a specific need without bloat, staying well within the ideal range for a focused service.
Completeness4/5
The server covers common PDF generation tasks: two conversion formats and two document types. Minor gaps like generic text-to-PDF or PDF manipulation exist, but the core workflows are well represented for its stated purpose.