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 explaining behavior. It clearly conveys a read-only time lookup, but it does not mention anything about output format, invalid timezone handling, or the fact that url, host, and json appear irrelevant to the stated purpose.
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 eight words, front-loaded, and contains no filler. Every word contributes to the core meaning, making it appropriately concise for a simple lookup tool.
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 description is adequate for a basic call, but it is incomplete given the schema's four optional parameters and no output schema. An agent receives no guidance about the output format or whether the non-zone parameters are ignored, leaving room for misinterpretation.
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 description is not expected to restate parameter meanings. It adds no new semantic value beyond the schema, and it does not clarify that only zone is likely relevant among the four optional properties, which would have been useful.
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's function precisely: it returns the current time for a named IANA timezone. This distinguishes it from siblings like utc-time, iana-zones, and weekday-utc, and it is not a mere tautology of the tool name.
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?
The description implies the tool should be used when the agent needs current local time for a named IANA timezone, and sibling names hint at alternatives for UTC or zone listing. However, it does not explicitly state when to avoid this tool or name an alternative.
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.
Tools cluster into URL/HTTP and time-related groups, but within each cluster the purposes are mostly distinguishable. citation, normalize-url, and domain-shape all touch hostnames, while timezone, utc-time, and weekday-utc all return current time data, so an agent could briefly hesitate when selecting among them.
All names use lowercase hyphens, but there is no consistent verb_noun or noun pattern. Some tools use verb-object naming like inspect-robots and normalize-url, while others are plain nouns like citation, timezone, and status-catalog, making the set feel inconsistent.
Eleven tools is a reasonable count for a utility server and does not feel bloated. However, the selection spans many unrelated concerns—URL parsing, time, JSON validation, robots.txt, HTTP status—so the set feels broader than a single focused purpose.
For a privacy-focused URL/HTTP utility set, there are notable gaps such as no redirect or header inspection, and for time utilities there is no timezone conversion tool. The surface covers basic atomic operations but lacks the cohesive lifecycle or workflow coverage that would make it feel complete.