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 |
Pacific/Auckland clock
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
D1.9/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, and the description only states the output without disclosing any behavior regarding the parameters. It is unclear whether passing url, host, json, or zone would alter the result, trigger side effects, or be silently ignored.
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 terse—a single sentence—which is concise but lacks any structural elements that would clarify usage or parameter handling. The brevity comes at the cost of essential information, making the tool difficult to invoke correctly.
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 and no explanation of parameter influence, the description is incomplete even for a simple timestamp tool. The agent has no way to infer the response format, error behavior, or whether the parameters are accepted but meaningless.
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?
The schema descriptions for url, host, json, and zone are clearly for other purposes (normalizing, citing, validating, timezone conversion) and do not match a UTC timestamp tool. The description offers no explanation of how these parameters relate to the output, leaving the agent unable to determine whether they are even relevant.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the current UTC timestamp, which is a specific and unambiguous function. However, it doesn't elaborate on the format or context of the timestamp, and the mismatch with the listed parameters slightly muddies the purpose.
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 like 'timezone' or 'tz-pacific-auckland'. The description does not mention that parameters are ignored, how to request a specific timezone, or any condition that would select this tool.
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.1/5.0
Disambiguation2/5
Several tools overlap heavily: timezone, tz-pacific-auckland, and utc-time all return current time, and URL/HTTP tools like citation, compatibility, normalize-url, and domain-shape have unclear boundaries. Agents would likely struggle to pick the right one.
Naming Consistency2/5
Names are mostly lowercase hyphenated, but mix verb-object forms (inspect-robots, normalize-url, validate-json) with noun-like labels (citation, compatibility, timezone) and an inconsistent specific alias (tz-pacific-auckland vs timezone).
Tool Count2/5
Eleven tools is not inherently excessive, but for a server named as a Pacific/Auckland clock, at least seven tools are unrelated URL/HTTP utilities and several time tools are redundant, making the set feel padded and poorly scoped.
Completeness3/5
The time-related subset covers current time, UTC, and IANA zone names, so it is largely complete for a simple clock. However, the mixed URL/HTTP and validation tools have no clear unified domain, leaving the overall surface incomplete and hard to reason about.