Skip to main content
Glama

get-certificate

get-certificate

Retrieve a specific SSL certificate by its numeric ID from an Nginx Proxy Manager instance; use list-certificates first to find the ID.

Instructions

Get a single certificate by ID. Use list-certificates to find the ID.

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>",
      "id": "<id>"
    },
    "name": "get-certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCertificate numeric ID
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral context. 'Get' implies a read operation, but it does not state permissions, failure behavior when the ID is absent, or return characteristics beyond the implied single certificate.

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 main action, and the alternative guidance is appended without wasted wording.

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 two-parameter read tool with no output schema, the description covers the core operation and ID lookup. However, it leaves the required `instanceName` parameter unexplained, which is a meaningful gap for correct invocation.

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 50%. The description adds useful meaning for `id` as the lookup key and explains how to obtain it via `list-certificates`, but it does not clarify the required `instanceName` parameter, which remains undocumented.

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 states a specific verb and resource: 'Get a single certificate by ID.' It distinguishes this retrieval operation from 'list-certificates' by emphasizing a single certificate and the ID lookup.

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

Usage Guidelines4/5

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

It gives explicit guidance to use `list-certificates` when the ID is unknown, which is the main alternative path. It does not cover error cases or when not to use the tool, but the guidance is clear for this simple read operation.

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