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?
With no annotations, the description carries the full burden of explaining behavior, but it only says 'current time' and does not disclose whether it performs a network lookup, how errors are handled, or whether it has side effects.
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 a single concise sentence with the main purpose front-loaded. However, it does not structure or relate the additional parameters, so some clarity is lost.
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?
The tool description is incomplete for correct use: it does not specify that 'zone' is required, does not describe the output format, and ignores the three unrelated parameters in the schema. An agent cannot reliably invoke this tool based on the provided context.
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?
The description is relevant only to the 'zone' parameter, while the schema also includes 'url', 'host', and 'json' with unrelated descriptions. This mismatch is highly misleading and leaves most parameters semantically unexplained.
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 states the tool returns the current time for a named IANA timezone, which is specific enough to distinguish it from sibling tools like utc-time and iana-zones. It lacks an explicit verb and return details, but the core purpose is clear.
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 guidance is given about when to use this tool instead of alternatives such as utc-time for UTC time or iana-zones for zone listings. The description does not mention context, prerequisites, or exclusions.
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.
citation, normalize-url, and domain-shape all operate on URLs and can return overlapping fields, while compatibility is vaguely described. The remaining tools are mostly distinct, but the URL-related overlap could cause misselection.
All names use lowercase kebab-case, but there is no consistent verb/noun pattern—e.g., inspect-robots and normalize-url are verb-first, while citation and utc-time are noun-like. Names such as cc-in and compatibility do not clearly signal their action.
With 11 tools, the count is reasonable and not bloated. However, the mix of country, URL, time, and JSON utilities suggests a broader toolkit than the server name implies.
As a set of read-only metadata and validation helpers, it covers URL, HTTP, robots, time, JSON, and a single country lookup. The domain is not clearly defined, and only one country record is exposed, so some workflows may lack a matching tool.