Common IANA timezone names for clock calls.
| 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 provided, the description carries the full burden of behavioral disclosure, but it merely names the data without stating that the tool returns a list, accepts or ignores parameters, or has no side effects. The four optional parameters are unexplained behaviorally, leaving the agent without a picture of what happens when the tool is invoked.
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 text is very short and free of redundancy, which is efficient, but it is structured as an incomplete fragment rather than a definition with a subject and verb. The brevity comes at the expense of the operational details an agent needs.
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 annotations, no output schema, and four optional parameters, the description should clarify whether this is a parameterless catalog, what response format to expect, and how it integrates with clock calls. It provides none of that, only a bare phrase that leaves too much to inference.
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 input schema provides 100% description coverage for all four parameters, so the schema already documents each parameter's meaning. However, the description adds no parameter-level context and does not explain why url, host, and json appear in a tool about IANA zones, which is a notable semantic gap even though it does not contradict the schema.
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 identifies the resource (common IANA timezone names) and hints at a domain (clock calls), but it lacks a specific verb such as 'returns' or 'lists', making it a noun phrase rather than a clear operational definition. It also does not distinguish this tool from the sibling 'timezone' tool, which could plausibly serve a similar purpose.
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 on when to use this tool versus alternatives, no exclusions, and no mention of sibling tools. The only hint is 'for clock calls', which is too vague to help an agent decide between this and related timezone tools.
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.