AgentRender

pdf

Convert a public URL into a PDF document. Returns JSON with base64-encoded PDF and receipt.

Instructions

Capture a public URL as a PDF. Returns JSON with pdf_base64 + receipt.

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": "pdf"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`landscape`	No
`print_background`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 22, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It adds useful context by restricting input to public URLs and by summarizing the JSON return shape as pdf_base64 + receipt. It does not disclose potential timeouts, rendering limitations, or other HTTP behaviors that might affect the call.

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?

Two short sentences, no filler, with the core action front-loaded and the return format kept to one clause. It is appropriately sized for a simple tool.

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?

For a low-complexity tool with an output schema, the definition covers the main action and return contract, but it omits explicit sibling differentiation and parameter semantics. An agent would have to guess at usage edge cases such as authenticated pages or orientation/background effects, so it is only minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not compensate: it only references the URL and says nothing about landscape orientation or print_background behavior. The boolean names are somewhat self-explanatory, but the description adds no meaning beyond the bare schema.

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 phrase 'Capture a public URL as a PDF' names a specific action, resource, and output format. It is clearly distinct from sibling tools 'screenshot' and 'extract', so an agent can tell what this tool is for.

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 this tool is for producing PDFs from publicly accessible URLs, but it does not explicitly state when to prefer it over 'screenshot' or 'extract'. It also does not mention exclusions such as private or authenticated pages, so usage guidance is left to inference.

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

Deploy Server

pdf