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 |
UUID Mint
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, but it only states 'Current UTC timestamp.' It does not clarify whether the four unrelated optional parameters are used or ignored, nor what format the timestamp is returned in.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise and front-loaded with the core purpose. It is a fragment rather than a full sentence, but it contains no wasted words.
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?
For a tool with no output schema and a confusing input schema, the description is under-specified. It fails to state the return format, whether parameters are optional or ignored, or how this tool differs functionally from time-related siblings.
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?
Schema coverage is 100%, but the parameter descriptions (URL, host, JSON, zone) do not relate to the tool's stated purpose of returning a UTC timestamp. The description adds nothing to reconcile these inputs, so the high schema coverage does not actually help an agent call this tool correctly.
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 'Current UTC timestamp' clearly names the resource and implies the action of retrieving it. It is distinguishable from time-related siblings like timezone and iana-zones because it explicitly says UTC, though it does not name or compare against alternatives.
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 provided about when to use this tool instead of alternatives such as timezone or iana-zones. An agent must infer the selection criteria from the name and description alone.
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.8/5.0
Disambiguation3/5
Most tools have distinct outputs, but citation and normalize-url both return URL components and overlap on host/scheme. The time-related tools (iana-zones, timezone, utc-time) share a domain, and compatibility is vague enough that an agent may struggle to select it correctly.
Naming Consistency3/5
All names are lowercase and kebab-case, which gives a consistent visual style. However, the naming mixes noun labels like citation and timezone with verb phrases like inspect-robots and validate-json, so there is no uniform verb_noun pattern.
Tool Count3/5
Eleven tools is a reasonable count, but the server is named 'UUID Mint' and contains a loose collection of URL, time, HTTP, JSON, and UUID utilities. The count is not excessive, but the tools do not form a cohesive, well-scoped set.
Completeness2/5
The tool surface is a grab bag with no coherent domain, so common workflows are only partially covered. For example, there is UUID generation but no UUID validation, timezone lookup but no timezone conversion, and URL inspection but no full URL parsing or content retrieval.