Skip to main content
Glama
IBM

chuk-mcp-time

by IBM
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_time_utc

Query multiple NTP servers to get consensus UTC time with high accuracy, compensating for network latency.

Instructions

Get current UTC time with high accuracy using NTP consensus.

Queries multiple NTP servers, removes outliers, and computes a consensus time
that is independent of the system clock. Returns detailed information about
all sources, consensus method, and estimated error.

By default, the returned timestamp is compensated for the time it took to
query NTP servers and compute consensus. This means the timestamp represents
the time when the response is returned, not when NTP servers were queried.

Args:
    mode: Accuracy mode - "fast" uses 3-4 servers, "accurate" uses 7 servers
    compensate_latency: If True, add query duration to timestamp (default: True)

Returns:
    TimeResponse with consensus time and metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNofast
compensate_latencyNo

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It details NTP queries, outlier removal, consensus computation, and latency compensation. Lacks mention of network dependencies or failure modes, but overall transparent.

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

Conciseness5/5

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

Description is concise, front-loaded with purpose, followed by method, parameters, and returns. No redundant sentences.

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

Completeness3/5

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

No output schema, so description mentions return type (TimeResponse with metadata) but not specific fields. Adequate for simple tool, but could detail error handling or output structure.

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?

With 0% schema coverage, description compensates well by explaining 'mode' (fast vs accurate) and 'compensate_latency' boolean. Adds meaning beyond schema defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it gets current UTC time using NTP consensus, distinguishing it from siblings like get_local_time or get_time_for_timezone. The verb and resource are specific.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the method and parameters but does not explicitly state when to use this tool over alternatives or when not to use it. Lacks comparisons to siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IBM/chuk-mcp-time'

If you have feedback or need assistance with the MCP directory API, please join our Discord server