utc-time
Current UTC timestamp.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | HTTPS URL to normalize or cite | |
| host | No | Public hostname | |
| json | No | JSON text to validate; discarded after the check | |
| zone | No | IANA timezone name |
America/Chicago clock
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
D1.1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It discloses no side effects, required permissions, return format, or error behavior. The phrase 'Current UTC timestamp.' is entirely opaque about what happens when the tool is invoked.
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?
The description is extremely short, but it is under-specified to the point of uselessness. It does not convey essential information about the tool's operation, and the brevity works against clarity. The structure is not helpful.
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?
There is no output schema and no explanation of what the tool returns, how input parameters are used, or what 'UTC timestamp' means in the context of the provided schema. The tool is contextually incomplete for an agent to invoke correctly.
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?
Though the schema covers all four parameters, their descriptions are generic and unrelated to the stated purpose of returning a UTC timestamp. For example, 'HTTPS URL to normalize or cite' and 'JSON text to validate' have no obvious connection to time. The parameter descriptions are misleading rather than informative.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Current UTC timestamp.' is a noun phrase and fails to state what the tool actually does. It does not specify any action or behavior, and it is unclear how the tool relates to the input parameters (url, host, json, zone). The purpose is effectively missing.
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?
No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, typical scenarios, or how this tool differs from sibling tools like 'timezone' or 'iana-zones'. The description gives no usable direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.2/5.0
Disambiguation3/5
Most tools have distinct inputs and outputs, but citation and normalize-url both inspect URLs, while timezone, tz-america-chicago, and utc-time all return current time. Descriptions clarify the differences, but compatibility is vague and could be confused with status-catalog or citation.
Naming Consistency3/5
All names are lowercase and hyphenated, which is readable, but they mix verb-led names like inspect-robots and normalize-url with noun-led names like citation, domain-shape, and status-catalog. There is no consistent verb_noun or action pattern across the set.
Tool Count2/5
Eleven tools is not inherently excessive, but for a server named 'America/Chicago clock' only four tools relate to time. The remaining seven URL, HTTP, robots, and JSON utilities are off-purpose, making the count feel bloated and unfocused.
Completeness3/5
The time-related tools cover current time in Chicago, UTC, named IANA zones, and a zone list, so the clock core is usable. However, there is no timezone conversion or date arithmetic, and the unrelated utilities do not form a coherent broader domain, leaving the overall surface incomplete.