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, but it only states the tool's function. It does not disclose behavior for invalid zone names, whether the result includes DST/offset, or any output format expectations.
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?
A single, front-loaded sentence with no filler. Every word contributes to the core purpose.
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 no annotations, no output schema, and a confusing 4-parameter schema, the description is too minimal. It does not specify the return shape, error behavior, or that 'zone' is the only applicable input.
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 schema contains url, host, and json parameters that are unrelated to a timezone lookup. The description references only 'IANA timezone' and does not clarify that the other three parameters should be ignored, leaving an agent uncertain which arguments are valid.
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 a specific action and resource: 'Current time' + 'named IANA timezone.' This clearly distinguishes the tool from siblings like normalize-url or validate-json, which have entirely different purposes.
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 gives no guidance about when to use this tool versus the sibling tools, nor does it mention that only the 'zone' parameter is relevant. An agent must infer usage entirely from the name and schema.
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 dissect URLs/hostnames, and status-catalog overlaps with citation's HTTP status reporting. compatibility is too vague to disambiguate, so an agent could easily pick the wrong URL-analysis tool.
All names are lowercase and hyphen-separated, which is readable, but the pattern is mixed: inspect-robots, normalize-url, and validate-json use verb-noun while citation, domain-shape, and status-catalog are nouns. This is inconsistent but not chaotic.
Ten tools is not inherently too many, but for a server named 'JSON Check' only validate-json is on-topic. The remaining nine are unrelated URL, HTTP, and time utilities, making the toolset feel like a grab bag rather than a scoped set.
As a JSON-checking server it is severely incomplete: only a boolean validity check is offered, with no schema validation, formatting, or JSON-path operations. As a general URL/HTTP utility it also lacks HTTP body access, redirect handling, and timezone conversion, so common workflows will hit dead ends.