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 |
Word count, text discarded
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals only that the tool returns a current UTC timestamp, but does not explain the return format, what happens if parameters are supplied, or whether any of the optional inputs modify the behavior. The mismatch between the simple description and the four-parameter schema is unexplained.
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 extremely concise with no wasted words, but it is under-specified relative to the four-parameter schema. The single sentence earns its place for clarity of purpose, but it does not provide enough structural context for the optional inputs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has four optional parameters, no annotations, no output schema, and a sibling 'timezone' tool, yet the description explains none of these relationships. An agent cannot confidently determine whether to pass a zone, whether the URL/host/json fields are ignored, or what exact value will be returned.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides 100% description coverage for all four parameters, so the baseline is 3 even without additional explanation. However, the description itself adds no semantic link between 'Current UTC timestamp' and the parameters, leaving an agent unable to infer how url, host, json, or zone relate to the tool's purpose.
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 specific about the resource and action. However, it does not differentiate this from the sibling 'timezone' tool, and the presence of unrelated parameters (url, host, json, zone) in the schema muddies what the tool actually does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives like the 'timezone' sibling. There are no exclusions, prerequisites, or context about which optional parameters would be relevant.
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.7/5.0
Disambiguation4/5
Most tools target distinct resources like URLs, hostnames, robots.txt, timezones, and JSON. The main overlap is between citation and normalize-url, which both expose host information from a URL, and between timezone and utc-time when the requested zone is UTC. Descriptions are generally clear enough to disambiguate.
Naming Consistency3/5
All names use lowercase-with-hyphens, but the pattern is mixed: some are verb-object like normalize-url and validate-json, while others are nouns like citation, timezone, and status-catalog. This is readable but not a consistent verb_noun convention.
Tool Count4/5
11 tools is within a reasonable range for a utility server, and each tool has a distinct small purpose. A few could be consolidated, such as utc-time with timezone or citation with normalize-url, but the count is not excessive.
Completeness3/5
The server covers basic URL inspection, time retrieval, JSON validation, and word counting, but notable gaps exist such as URL validation, timezone conversion, HTTP header inspection, and JSON formatting. The surface is more of a grab bag than a coherent full-featured utility domain.