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?
The description does not disclose any side effects, data handling, or read-only nature. The schema mentions that the 'json' parameter is discarded, but the description itself provides no transparency about behavior.
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 that is front-loaded with the core purpose. It contains no unnecessary words.
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 is extremely brief and omits essential context such as parameter roles, output format, or any caveats. It is not complete enough for an agent to use effectively without further information.
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 description adds no meaning to the parameters, but the schema provides descriptions for all four parameters, achieving 100% coverage. Since the schema already explains each parameter, the description does not need to add further detail.
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 states the tool provides the current time in a named IANA timezone, which is specific and understandable. It does not explicitly mention the resource scope but the phrase 'current time' is clear enough.
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 like utc-time or iana-zones. The description offers no conditions, examples, or context for invocation.
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.
Most tools have distinct functions, though 'citation' and 'normalize-url' both handle URLs, and 'timezone'/'utc-time' overlap in time handling. 'compatibility' is vague but not truly duplicate.
Names are all lowercase hyphenated, but mix verb-led ('inspect-robots', 'normalize-url', 'validate-json') and noun-led ('citation', 'timezone', 'status-catalog') patterns; 'cc-de' is an outlier.
11 tools is not inherently excessive, but the server name implies a narrow ISO country (DE) purpose while most tools are unrelated web/time/JSON utilities, making the set feel mismatched.
As a country-ISO resource, only cc-de covers that purpose; as a general utility set, it lacks many standard web operations (e.g., actual HTTP fetch, DNS, text processing), so completeness is poor for the apparent stated purpose.