Skip to main content
Glama
Sign In
@kognar/nginx-manager-mcp-server

@kognar/nginx-manager-mcp-server

by kognar-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List certificates

npm_list_certificates

List all SSL certificates managed by Nginx Proxy Manager to review expiration dates and related entities.

Instructions

List all SSL certificates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "npm_list_certificates"
  }
}

Input Schema

NameRequiredDescriptionDefault
expandNoOptional expand fields (e.g. ['owner','certificate'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

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 must disclose behavior. It states the action but omits details like authentication requirements, response format (list of objects), or potential pagination. It is adequate for a simple read operation but lacks depth.

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?

Single sentence, zero waste. Front-loaded with the core purpose.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description is minimally complete. It could mention that the response is a list of certificate objects or include a note about the expand parameter's effect.

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 coverage is 100%, and the description adds no extra meaning beyond the schema's description of the 'expand' parameter. Baseline score of 3 is appropriate.

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?

The description 'List all SSL certificates' clearly states the verb (list) and resource (SSL certificates), distinguishing it from sibling list tools for other resources. However, it could be more specific about the scope (e.g., all certificates for the user or system).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like npm_get_certificate for a single certificate or other list tools. No context on prerequisites or exclusions.

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

Deploy Server

Other Tools