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 describing side effects, read-only behavior, or network access. The description does not disclose whether the tool performs any state-changing operations or if it is a safe, read-only lookup.
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 no extraneous words or repetition. It is easily scannable and to the point.
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 does not explain which parameter to use, how to format the timezone name, or what output format to expect. The mismatched schema parameters create additional ambiguity, making the tool description incomplete for reliable invocation.
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 includes url, host, json, and zone, but only zone is relevant to the description. The parameter descriptions for url, host, and json appear copied from other tools and are misleading in this context. The description does not clarify that these extra parameters are irrelevant or ignored.
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 clearly identifies the resource as the current time in a named IANA timezone, which distinguishes it from sibling tools like utc-time. However, it lacks an explicit verb such as 'returns' or 'gets', so it is slightly less direct than ideal.
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 provided on when to use this tool versus alternatives such as utc-time or iana-zones. The description only states what the tool does, not when it should be selected.
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.
Each tool name and description clearly targets a distinct function (URL parsing, timezone lookup, JSON validation, etc.), with no overlap or ambiguity.
All tool names use a consistent lowercase-hyphenated format (e.g., 'normalize-url', 'status-catalog'), following a uniform naming convention.
11 tools is a reasonable number for a general utility set, though some tools (like 'citation' and 'compatibility') seem abstract and may overlap conceptually with others.
The server name 'Miles to kilometers' implies a unit conversion focus, but none of the tools perform any unit conversion. The toolset is a hodgepodge of unrelated utilities, making it incomplete for its stated purpose.