Skip to main content
Glama
MCP Dokploy Online
by igoruam

certificates-one

Read-onlyIdempotent

Retrieves a single Dokploy certificate by its ID so you can inspect certificate details for deployment and infrastructure management.

Instructions

GET /certificates.one

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": {
      "certificateId": "<certificateId>"
    },
    "name": "certificates-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
certificateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, and 'GET' is consistent with them, so there is no contradiction. Beyond that the description adds nothing: no indication of what a missing certificate returns, whether the lookup reaches a remote provider, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity comes from omission rather than discipline; a raw endpoint path is not a front-loaded explanation of what the tool does. Every word spent is a restatement of the name.

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

Completeness1/5

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

For a tool with a required, undocumented identifier and no output schema, the description should carry the full burden of explaining input meaning and return shape. It supplies neither, leaving the definition unusable without experimentation.

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

Parameters1/5

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

The single required parameter certificateId has 0% schema description coverage, so the schema gives no semantics at all, and the description does not mention the parameter. The agent learns nothing about the identifier's format, origin, or scope from either source.

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

Purpose2/5

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

"GET /certificates.one" restates the tool name as an HTTP route and nothing more. It implies fetching a single certificate rather than a list, but it never states the verb+resource in plain language, so the agent must infer that 'one' means single-resource retrieval and that 'certificates' means TLS certificates.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of when not to use it, and no reference to the obvious alternative certificates-all. An agent choosing between single-item and list retrieval gets no help from the definition.

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