Skip to main content
Glama
MCP Dokploy Online
by igoruam

port-one

Read-onlyIdempotent

Retrieves details for a specific port by its ID from your Dokploy instance, letting you inspect port configuration and status.

Instructions

GET /port.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": {
      "portId": "<portId>"
    },
    "name": "port-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
portIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so safety and repeatability are covered structurally. The description adds nothing beyond that: no note on error behavior for an unknown portId, no indication whether the response is live state or cached, and no scoping context. It does not contradict the annotations, but it contributes no behavioral value.

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 a single fragment, so there is no wasted wording, but brevity here comes from under-specification rather than economy. There is no front-loaded statement of purpose an agent can act on.

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 whose entire interface is a single undocumented identifier, the definition supplies no usable context: not the meaning of portId, not what the returned port representation contains, and not how it relates to the sibling port-mutation tools. The description is effectively a bare route stub.

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?

One required parameter with 0% schema description coverage, and the description says nothing about it. It never clarifies whether portId is a numeric port number, a resource identifier, or a name, which is exactly the ambiguity that matters for an openWorld API. The only meaning available is the schema's type and minLength constraint.

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 /port.one" restates the tool name and an HTTP route rather than describing the tool's job. The method hint (GET) and the "one" suffix weakly imply fetching a single port record, but an agent gets that already from the name plus readOnlyHint; no verb like "retrieve" and no statement of what a port object is.

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 exclusions, and no mention of the siblings that list or mutate ports (port-create, port-update, port-delete, ports-one). Nothing tells the agent it should call this only when it already has a port identifier.

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