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 provided, so the description carries the full burden of behavioral disclosure. It states the basic output (current time) but does not explain behavior for invalid timezone names, whether the other schema parameters are ignored, or what format or precision the time 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise and front-loaded, with no wasted words. However, it is under-specified for a tool with four optional parameters and no annotations or output schema, making the brevity cost more than it saves.
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?
With no output schema and no annotations, the description should explain return values, input expectations, and behavior. It does none of these, and the mismatched schema parameters are left unexplained, so the definition is not complete enough for confident invocation.
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 coverage is 100%, so the baseline is 3, but the description adds no parameter-level meaning. The schema includes url, host, and json parameters that are unrelated to timezone semantics, and the description does not clarify whether they are relevant, ignored, or combined with zone. An agent can only guess that zone is the intended input.
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 clearly states that the tool returns the current time for a named IANA timezone, which is a specific and meaningful behavior. It is not a tautology and is distinguishable in intent from siblings like iana-zones and utc-time, though it does not explicitly name them.
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?
There is no guidance about when to use this tool versus alternatives such as utc-time or iana-zones, and no exclusions or prerequisites are mentioned. The description implies a use case but does not actually state when the tool should be selected.
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.
Most tools are distinct, but several overlap around URLs and time: citation, normalize-url, and domain-shape all operate on URLs/hostnames, while iana-zones, timezone, and utc-time overlap in purpose. The compatibility tool is especially vague and could be confused with citation or status-catalog.
Names are mostly lowercase and hyphenated, but the set mixes noun-style names like citation, timezone, and status-catalog with verb-style names like inspect-robots, normalize-url, and validate-json. There is no consistent verb_noun or noun-only convention, though the names remain readable.
Eleven tools is not an unreasonable count on its own, but the set feels scattershot relative to the server name 'ISO country US,' which implies a focused country-data service. Only one tool actually relates to the country domain, while the rest span unrelated web, URL, time, and JSON utilities.
As a collection of lightweight, privacy-oriented utilities, the surface is reasonably broad. However, the country-data aspect is severely thin with only cc-us, and there are notable gaps like DNS or HTTP header inspection if this is meant to be a general web-utility server.