Skip to main content
Glama
Sign In

IntoDNS.ai DNS & Email Security Scanner

by ai.intodns
OverviewDiscussionsAdmin

PDF report link

get_pdf_report_link
Read-onlyIdempotent

Build the direct PDF report endpoint URL for a domain. Pure URL construction — no scan triggered, no network call from this tool. Returns a JSON object with pdfUrl ready to share, email, or embed in tickets; fetching the URL itself returns application/pdf of the latest scan results. Use for downloadable shareable reports; use get_badge_link for an embeddable SVG status badge instead, or create_report_snapshot for an immutable hashed evidence URL. No auth.

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": {
      "domain": "<domain>"
    },
    "name": "get_pdf_report_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name only, e.g. example.com (no URL, path, or port)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond annotations: clarifies that no scan is triggered, no network call occurs, the return value is JSON with `pdfUrl`, the fetched URL serves `application/pdf` of the latest scan, and no auth is needed. This disambiguates the openWorldHint annotation rather than contradicting it.

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?

Front-loaded with the core behavior, then scope caveat, then return value, then alternatives and auth. Dense but every clause carries decision-relevant information.

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?

No output schema exists, and the description fully compensates by describing the returned JSON (`pdfUrl`) and what fetching it yields. Nothing an agent needs to call this 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?

Single required `domain` parameter with 100% schema description coverage, so the schema already documents the name-only format. The description adds no extra input meaning, matching the baseline for fully documented schemas.

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?

Specific verb+resource ("Build the direct PDF report endpoint URL for a domain") with an explicit scope statement ("Pure URL construction — no scan triggered"). It names the sibling alternatives get_badge_link and create_report_snapshot, so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

Explicitly states when to use it ("Use for downloadable shareable reports") and names the alternatives with their distinguishing conditions (get_badge_link for embeddable SVG, create_report_snapshot for immutable hashed evidence URL).

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

All IntoDNS.ai DNS & Email Security Scanner 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