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 behavioral disclosure. It only says 'Current time' and does not describe output format, error behavior for invalid zones, or whether the operation is read-only or network-dependent. This is minimal for a simple read tool but not sufficient without annotations.
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 one short sentence with no filler and front-loads the core behavior. However, it is so terse that it omits usage guidance and parameter disambiguation.
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 a schema containing unrelated optional parameters, the description is too thin. It does not state which parameter to pass, what the response looks like, or how it differs from utc-time. An agent cannot confidently invoke it correctly.
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 documents all four parameters, but three of them (url, host, json) are unrelated to timezone and appear to belong to sibling tools. The description only reinforces 'IANA timezone name' for zone and does not clarify that the other parameters are irrelevant or ignored, creating confusion despite high schema coverage.
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 returns the current time for a named IANA timezone, which is specific enough to distinguish it from utc-time and iana-zones. It lacks an explicit imperative verb, but the resource and scope are clear.
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 given about when to use this tool versus utc-time or iana-zones, and there is no mention of required inputs or fallback behavior. The intended context is implied but never explicitly stated.
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 are individually distinct in their operations, but the mix of URL, timezone, JSON, and temperature topics creates confusion about which tool applies to a given task. Names like 'compatibility' and 'citation' are vague and could be misinterpreted.
Naming conventions are inconsistent: some tools use hyphenated lower-case (f-to-c, iana-zones), others use single words (citation, timezone), and some use multi-word phrases (normalize-url, validate-json). This lack of a uniform pattern reduces predictability.
At 11 tools, the count is within the typical range, but it feels excessive for a server ostensibly dedicated to Fahrenheit-to-Celsius conversion. The number is inflated by unrelated utilities, making the set poorly scoped for the stated purpose.
For a Fahrenheit-to-Celsius converter, there is only one relevant tool (f-to-c). Essential operations like Celsius-to-Fahrenheit, Kelvin conversions, or batch conversions are missing, so the domain coverage is severely incomplete.