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 |
Europe/Berlin clock
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
D1.5/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations and the description does not disclose whether the listed input parameters (url, host, json, zone) are ignored or relevant. The tool's behavior regarding parameters and return format is completely opaque.
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?
The description is very short, but it sacrifices essential information about parameters and output format. It is concise but not appropriately sized for the tool's actual interface.
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?
The description omits the output format (e.g., ISO 8601), parameter handling, and any relationship to sibling timezone tools. Given the misleading input schema, this is far from complete.
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 input schema contains four parameters with descriptions entirely unrelated to UTC time (e.g., url, host, json, zone). The tool description provides no explanation for why these parameters exist or how they affect the output.
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 'Current UTC timestamp' names the output but uses no verb and doesn't explicitly distinguish this tool from sibling timezone tools like timezone or tz-europe-berlin. The purpose is partially clear but lacks resource/action framing.
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 given for when to use this tool versus the sibling timezone tools. The description does not mention that this tool is for UTC-only needs or when a different timezone tool would be appropriate.
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/5.0
Disambiguation2/5
Several tools overlap in purpose: timezone, tz-europe-berlin, and utc-time all return current time, and citation/normalize-url both analyze URL components. 'compatibility' is too vague to distinguish from the other HTTP/classification tools.
Naming Consistency3/5
All names are lowercase and hyphenated, which is a consistent delimiter style, but the pattern mixes verb phrases (inspect-robots, normalize-url, validate-json) with noun phrases (citation, compatibility, status-catalog). There is no uniform verb_noun or noun_noun convention.
Tool Count2/5
Eleven tools is not excessive in raw count, but the server is named as a clock and only four tools (timezone, tz-europe-berlin, utc-time, iana-zones) support that purpose. The rest are unrelated web/HTTP/JSON utilities, making the set poorly scoped.
Completeness2/5
For the clock domain, time lookup is covered but timezone conversion is missing. For the broader web/HTTP utilities hinted at by the other tools, the surface is incomplete and lacks a clear lifecycle or workflow, so agents would hit dead ends.