Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-checkGPUStatus

Read-onlyIdempotent

Check GPU status for a Dokploy server by passing its server ID to verify GPU availability and health.

Instructions

GET /settings.checkGPUStatus

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "settings-checkGPUStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

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's "GET" merely repeats that. It adds no context about what the call does when GPU data is unavailable, whether authentication is needed, or how costly the check is.

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 brevity here is under-specification rather than conciseness: a single route string with no front-loaded purpose statement or structure. Nothing is wasted because nothing informative is present.

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?

With no output schema, an undocumented optional parameter, and a description consisting solely of a route, an agent has essentially no information beyond the tool name. The definition is inadequate for correct invocation, especially the semantics of omitting serverId.

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 serverId property, and the description does not mention it at all. An agent cannot tell whether omitting serverId returns status for all servers, the local server, or errors out, so the description fails to compensate for the schema gap.

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 HTTP route "GET /settings.checkGPUStatus", which restates the tool name rather than explaining what is checked or returned. An agent can infer it reads GPU status from the name, but nothing about scope (per-server? global?) or the meaning of "status" is conveyed.

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 on when to use this tool, when not to, or how it relates to siblings such as settings-health or settings-checkInfrastructureHealth. The only implicit signal is the GET verb, which does not distinguish it from the other read-only settings tools.

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