Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-readAppMonitoring

Read-onlyIdempotent

Retrieve monitoring metrics for a Dokploy application by its app name, so you can inspect resource usage and health data for that deployment.

Instructions

GET /application.readAppMonitoring

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": {
      "appName": "<appName>"
    },
    "name": "application-readAppMonitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNameYes

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say what monitoring payload comes back, whether an app must be running, or how errors surface for an unknown appName.

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 with no wasted words, but that is under-specification rather than concision. Dumping a raw route string is not front-loaded, purposeful prose.

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 one fully undocumented required parameter, no output schema, and no annotations explaining return shape, the description supplies none of the missing information needed to call it correctly or interpret the result.

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?

Schema description coverage is 0% for the single required parameter appName, and the description provides no compensating meaning — no format, no example, no indication of whether it is a container name, stack name, or Dokploy app identifier. All semantic burden is unmet.

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 string 'GET /application.readAppMonitoring', which restates the tool name rather than describing what monitoring data is read. The only added signal is the HTTP verb, implying a fetch. It does not distinguish this from siblings such as application-readLogs or admin-setupMonitoring.

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 guidance about when to use this tool, no prerequisites, and no mention of alternatives like application-readLogs for log retrieval. The agent must infer everything from the name and the sibling list.

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