Skip to main content
Glama

list-certificates

list-certificates

Retrieve all SSL/TLS certificates from an Nginx Proxy Manager instance, including Let's Encrypt and manual certificates, to review or manage them.

Instructions

List all certificates on an NPM instance. Includes Let's Encrypt and manual certificates.

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": {
      "instanceName": "<instanceName>"
    },
    "name": "list-certificates"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does add real content context by disclosing that both Let's Encrypt and manual certificates are returned, so an agent knows one call covers both types. It says nothing about read-only safety, result ordering, or whether large instances are truncated/paginated.

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, front-loaded with the verb and scope, and the second sentence earns its place by clarifying what certificate types appear in the results. No filler or restated title.

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 simple single-parameter read tool with no output schema, the description is adequate to call it, but it omits what a returned certificate record contains and whether results are paginated or filtered. Those gaps are modest but leave the agent guessing about result shape.

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?

There is one required parameter, instanceName, with 0% schema description coverage, and the description never explains it beyond the phrase "on an NPM instance". No format, source, or validity expectations are given, so the description does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List all certificates on an NPM instance" gives a specific verb (List) and resource (certificates) with explicit scope (all, per instance), which separates it from the singular get-certificate sibling. It stops short of naming a sibling outright, so it is clear but not maximally differentiated.

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?

Usage is only implied: "List all" signals an unfiltered enumeration, from which an agent can infer this is for discovery rather than fetching one certificate. There is no explicit when-to-use, when-not, or routing to get-certificate/renew-certificate.

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