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?
There are no annotations, and the description does not disclose that the schema includes url, host, and json parameters that appear unrelated to timezone lookup. This mismatch can mislead an agent into passing those parameters. It also doesn't state whether extra parameters are ignored or rejected.
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 extremely concise and easy to parse, with no extraneous words. It sacrifices necessary disambiguation but is well-structured.
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?
Given the mismatched schema, the description is too sparse to resolve ambiguities or explain how the extra parameters relate to the tool. It also omits any note about return format or side effects, making it incomplete for reliable selection.
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 schema provides descriptions for all parameters, but the description only reinforces the zone parameter. It adds no clarification for url, host, or json, which seem copied from other tools and conflict with the tool's purpose.
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?
Description clearly states the tool's purpose as returning current time in a named IANA timezone, which distinguishes it from sibling tools like utc-time and iana-zones. However, it does not explicitly use an imperative verb or mention that the schema contains unrelated fields.
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?
Description implies use when a local time in a named IANA timezone is needed, rather than UTC or zone listing. It does not explicitly state when not to use it or mention alternatives, leaving usage guidance implicit.
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.
Several URL-centered tools (citation, normalize-url, domain-shape) and time tools (timezone, utc-time) overlap in input type and could be confused, though their output purposes are mostly distinct. The vague 'compatibility' tool lacks a clear boundary, and 'lang-hi' seems unrelated to the rest.
All names use lowercase kebab-case, which gives a consistent visual pattern, but the grammatical style is mixed: some are verbs (normalize-url, validate-json), some nouns (citation, timezone), and some are opaque (compatibility, lang-hi). It is readable but not a clean verb_noun convention.
With 11 tools, the count is within a reasonable range for a utility server and not bloated. However, a few tools feel like one-offs or constants (lang-hi, iana-zones), so the set does not feel perfectly curated.
The tool surface is a grab bag of URL, HTTP status, robots, time, JSON, and language utilities, so there is no coherent domain to complete. For a web/URL toolkit, obvious operations like header inspection, content fetch, or DNS/WHOIS are missing; for a language server, only a tag constant is present.