Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-one

Read-onlyIdempotent

Fetches details for a single Dokploy application using its application ID, enabling targeted inspection and management of deployed apps.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

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, idempotentHint and openWorldHint, so the description carries a lower burden, but it adds nothing beyond them - no statement about what is returned or what happens when the application is absent. It does not contradict the read-only annotation, since GET implies a read.

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?

The text is not verbose, but it is under-specified rather than concise: a bare route string with no front-loaded statement of purpose or return behavior. Nothing in it earns its place over the tool name alone.

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 read tool with an undocumented required parameter and no output schema, the description supplies none of the missing pieces - neither the identifier semantics nor the shape of the returned application. An agent cannot call this confidently from the definition alone.

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?

There is one required parameter, applicationId, at 0% schema description coverage, and the description says nothing about its format or accepted values. With a low-coverage single parameter, the description should compensate and does not.

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?

The description is only the raw route 'GET /application.one', which restates the tool name rather than explaining what it returns. An agent can infer a single-application read from 'GET' plus the singular 'one', but 'application.one' is an opaque identifier that conveys no domain meaning.

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 prerequisites, and no mention of how this differs from siblings such as application-search or domain-byApplicationId. The agent must guess that this fetches one application by ID rather than searching.

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