Skip to main content
Glama

delete-certificate

delete-certificate

Deletes a certificate by ID, but only if no proxy host references it. Use to remove unused certificates.

Instructions

Delete a certificate by ID. Only certificates not referenced by proxy hosts can be deleted.

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": "delete-certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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. It does disclose one important behavioral trait beyond the schema: a referential-integrity constraint that can cause the operation to be rejected. It does not state that deletion is irreversible, which permission level is required, or how failures are surfaced.

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, zero filler, with the core action front-loaded and the eligibility constraint following immediately. Nothing is redundant or padded.

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 destructive two-parameter tool with no annotations and no output schema, the description covers the action and the main blocking condition but leaves instanceName undefined and omits irreversibility, required permissions, and error behavior. Adequate to attempt a call correctly, not to anticipate failure modes.

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?

Schema description coverage is 0% for two required parameters, so the description must compensate. "By ID" loosely clarifies the id parameter's role, but instanceName is never mentioned and neither parameter's format, source, or scope is explained.

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?

States a precise verb and resource ("Delete a certificate by ID") and immediately adds the scoping constraint that only unreferenced certificates are eligible. The verb distinguishes it cleanly from sibling operations like create-certificate, get-certificate, and renew-certificate, though no sibling is named explicitly.

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 eligibility precondition ("only certificates not referenced by proxy hosts") tells the agent when a delete will fail, which is useful implied guidance. However, it gives no positive guidance on prerequisites or next steps — e.g., that the agent should list-certificates to obtain the ID or get-proxy-host to confirm no reference exists, or that delete-proxy-host may need to run first.

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