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 |
Language it
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No behavioral traits are disclosed. There is no mention of network requests, side effects, or dependencies. The description is purely a statement of output with no explanation of how the tool behaves.
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?
The description is a single concise sentence, 'Current UTC time,' which is efficient and easily understood. There is no unnecessary verbosity.
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?
Given the complexity of the input schema with four parameters that appear unrelated, the description is severely incomplete. It fails to explain how the parameters affect the output, whether they are required, or any other contextual details needed to use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although the schema provides descriptions for each parameter (url, host, json, zone), these descriptions are about unrelated tasks like URL normalization, JSON validation, and timezone names. The tool description does not explain how these parameters relate to obtaining the current UTC time, so the parameter semantics are confusing and not helpful.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'Current UTC time,' clearly indicating the tool provides the current UTC time. However, the input schema contains parameters for URL, host, JSON, and timezone, which are unexplained and seem unrelated, creating confusion about the tool's actual 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 others. The description lacks any conditions, examples, or differentiation from sibling tools.
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 in purpose: citation, normalize-url, and domain-shape all analyze URLs/hostnames, while iana-zones, timezone, and utc-time all relate to time. compatibility is vague and could be confused with citation or status-catalog. Only a few tools have truly distinct, non-overlapping functions.
Naming Consistency3/5
All names use lowercase hyphenation, which is a consistent visual style. However, the pattern is inconsistent: some are imperative verbs (normalize-url, inspect-robots, validate-json) while others are noun phrases (citation, compatibility, timezone, status-catalog). The names are readable but do not follow a predictable verb_noun convention.
Tool Count4/5
Eleven tools is a reasonable count for a utility server and falls within the typical well-scoped range. Some tools feel trivial or overlapping, such as lang-it and the multiple time-related tools, but the total is not excessive.
Completeness2/5
The tool set has no coherent unifying domain: it mixes URL parsing, HTTP status, time, JSON validation, robots.txt, and a language tag. Obvious operations like URL validation, timezone conversion, or HTTP status details are missing, and the grab-bag nature makes it impossible to assess complete lifecycle coverage.