Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-getServerTime

Read-onlyIdempotent

Retrieve the current server time from your Dokploy instance to verify clock synchronization and support timestamp-dependent deployment and infrastructure tasks.

Instructions

GET /server.getServerTime

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-getServerTime"
  }
}

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=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description contributes nothing beyond that—no mention of what value is returned, its timezone/format, whether it requires authentication, or whether it hits a remote host (relevant given openWorldHint).

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 certainly short and front-loaded, with no wasted clauses, but the brevity is under-specification rather than effective concision—the single route token is the entire definition and leaves the agent with no operational detail.

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-parameter read tool, the definition is arguably survivable, but with no output schema the description should state at minimum that it returns the server's current time and in what form (epoch, ISO-8601, timezone). As written, the agent cannot know what to expect from the response.

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?

There are zero parameters, so per calibration the baseline is 4. The empty object schema with additionalProperties=false is self-explanatory and the description has nothing it could usefully add about arguments.

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 a raw route string, 'GET /server.getServerTime', which essentially restates the tool name and title rather than describing the operation in prose. It does convey the HTTP verb and resource, but adds no specificity an agent could not already infer from 'server-getServerTime'.

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?

No when-to-use guidance is present, no mention of prerequisites, and no distinction from sibling probes such as docker-getServerHealth or server-getServerMetrics. The agent must infer that this is a lightweight clock/health-style read purely from the name.

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