Current time in a named IANA timezone.
| 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 |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description must carry the behavioral burden. It implies a read-only lookup but never states whether it makes a network call, what side effects it has, or how the time is obtained and returned.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with no filler and the core resource front-loaded. It is appropriately terse, though it would earn a higher score with an explicit verb and usage context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 no annotations, the description is incomplete: it does not specify the return format, the parameter to use, or how this differs from utc-time. The schema even lists four parameters, and the description does not clarify which are relevant.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3; each parameter already has a description. The description adds no parameter-level detail and does not warn that url, host, and json appear unrelated to timezone lookups.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific resource (named IANA timezone) and the result (current time), which clearly conveys the tool's core function and distinguishes it from the sibling utc-time. It is not a full verb phrase ('Returns current time...'), but the intent is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use or when-not-to-use guidance is given; there is no mention of the utc-time sibling or any alternative for UTC vs named zones. Usage is only implied by the tool name and the one-line description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The time-related tools (epoch-ms, utc-time, timezone, iana-zones) are distinguishable, but several URL tools overlap in input and output: citation and normalize-url both expose host/URL components, and compatibility is vague about what it classifies. An agent could misselect between the URL inspection tools despite helpful descriptions.
Names are mostly lowercase with hyphens, but there is no consistent grammatical pattern: noun phrases like epoch-ms, utc-time, and status-catalog mix with imperative verbs like inspect-robots, normalize-url, and validate-json. This inconsistency makes the naming style readable but unpredictable.
Eleven tools is a reasonable count on its own, but the set is not tightly scoped to the server's apparent identity of Unix epoch milliseconds; it mixes time, URL, robots, status code, and JSON utilities. This feels like a general utility grab-bag rather than a focused toolset.
For the time domain implied by the server name, there are no epoch-to-date conversions, formatting helpers, or timezone offset details, leaving obvious gaps. The URL/request utilities are similarly fragmentary, covering shape and status but not full content retrieval or more useful metadata, so the surface feels incomplete for any single stated purpose.