nowsecure-mcp-server

download_assessment_pdf

Download assessment PDF report via REST API endpoint, with graceful error handling if rendering fails.

Instructions

Attempt to download NowSecure's own PDF via the REST report endpoint (/report/assessment/ref/{ref}.pdf). This is a different code path than the broken UI export and may succeed. Falls back gracefully with an error if NowSecure's renderer also fails.

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": {
      "assessmentRef": "<assessmentRef>",
      "outputPath": "<outputPath>"
    },
    "name": "download_assessment_pdf"
  }
}

Input Schema

Name	Required	Description
`assessmentRef`	Yes	Assessment ref (UUID).
`outputPath`	Yes	Where to write the PDF.
`onlyRemediation`	No	If true (default), filters to open/detected findings with remediation resources and hides screenshots.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jun 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the attempt via a specific endpoint and fallback on error, but lacks details on permissions, rate limits, or whether it's read-only.

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 sentences, front-loaded with action, no wasted words. Concisely conveys purpose and context.

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?

Description covers the core action and fallback but does not explain return values or output format. For a simple download tool, this is adequate but not fully 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 description coverage is 100%, so baseline is 3. The description adds no additional parameter meaning beyond the 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 description clearly states the tool's purpose: downloading a PDF assessment via a specific REST endpoint. It differentiates from the broken UI export and from siblings like generate_remediation_pdf by focusing on the assessment PDF.

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 gives context for when to use (when UI export is broken) and notes graceful fallback, but does not explicitly state when not to use or compare with alternatives like generate_remediation_pdf.

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

Deploy Server