Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-count

Read-onlyIdempotent

Retrieve the total number of servers configured in your Dokploy instance to monitor infrastructure size and verify deployment targets.

Instructions

GET /server.count

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": "server-count"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds nothing beyond the endpoint string – no indication of what the count covers (global vs. permission-scoped) or how it relates to server-all. No contradiction, but essentially zero added behavioral context.

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

Conciseness3/5

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

It is extremely short, which is fine, but the terseness is under-specification rather than efficient structure. There is no prose sentence, just a route string, so there is nothing to front-load.

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

Completeness2/5

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

For a trivial no-param read endpoint the annotations carry safety, but the description still does not tell the agent the return value (an integer count?) or when this is preferable to server-all. With no output schema, response-shape clarity is entirely missing.

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

Parameters4/5

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

Zero parameters, so the baseline is 4. The empty schema is consistent with a no-argument count endpoint and needs no compensation in the description.

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 "GET /server.count" – the raw HTTP route restated. It implies counting servers but gives no prose statement of purpose and does not distinguish it from siblings such as server-all or server-getServerMetrics. This is effectively a restatement of the name/endpoint rather than a purpose statement.

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

Usage Guidelines2/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 alternatives (e.g., server-all for the actual list), and no exclusions. The agent must infer that this is a lightweight count rather than a full list retrieval.

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