nginx-proxy-manager-mcp

npm_download_certificate

Download a certificate, private key, or chain in PEM format from Nginx Proxy Manager. Provide the certificate ID and choose pem, key, or chain format.

Instructions

Download a certificate, its private key, or the chain (PEM).

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": {
      "id": "<id>",
      "format": "<format>"
    },
    "name": "npm_download_certificate"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`format`	Yes	pem=cert, key=private key, chain=chain

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 4, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it does not specify whether this is a read-only operation, the response format, required permissions, or error behavior. The agent must guess at the tool's safety and side effects.

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 a single, direct sentence with no redundant words. It front-loads the primary verb and resource, making it scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema and no annotations, yet the description is extremely minimal. It does not explain what 'Download' returns (e.g., file content versus path), nor does it address prerequisites, validation, or edge cases. This incompleteness could lead to incorrect invocation.

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

Parameters2/5

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

The schema covers 'format' with a description and enum, and the tool description echoes the variants (pem, key, chain) without adding new meaning. The 'id' parameter is undocumented in both the schema and description, leaving its purpose unclear. With only 50% schema coverage, the description does not adequately compensate for the missing id explanation.

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 action ('Download') and the specific resources ('certificate', 'private key', 'chain'), with the format distinction explicit. It differentiates the tool from sibling tools like create/renew/delete by focusing on retrieval.

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 usage through the verb 'Download' but provides no explicit when-to-use guidance or comparisons to alternatives. There is no mention of contexts where a sibling tool would be preferred, so the guidance is purely inferred.

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