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 only states the output ('current time') and does not disclose whether the tool has side effects, errors, or constraints. With no annotations provided, the description carries the full burden of behavioral transparency and falls short.
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 extremely concise and free of unnecessary information. It states the core purpose in a single short sentence.
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 simple time lookup tool, the description is minimally adequate but omits useful context such as expected output format, handling of invalid timezone names, and whether the tool is read-only. It is complete enough for basic understanding but not fully robust.
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 includes four parameters, but the description only explains 'zone'. The roles of 'url', 'host', and 'json' are unclear in the context of this tool, and there is no explanation of how they relate to the described functionality.
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 returns the current time for a named IANA timezone, which distinguishes it from generic time tools. However, it lacks an explicit action verb like 'get' or 'retrieve', slightly reducing clarity.
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. The description does not mention any conditions or preferences that would help an agent choose this tool.
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 purposes (URL inspection, time, status codes, JSON validation), but citation and normalize-url both deal with URL parts and could cause confusion. compatibility is also somewhat vague, though it appears to classify requests differently.
All tool names use lowercase with hyphens (e.g., domain-shape, utc-time, validate-json), forming a consistent and predictable pattern across the entire set.
11 tools is within a reasonable range, but the server lacks a unified focus—it's a grab bag of utilities. While not excessive, the count feels high for the apparent scope, which is unclear and fragmented.
There is no coherent domain to assess completeness against. The server is labeled 'Language es' but only one tool (lang-es) relates to language, leaving many potential gaps. For a general utility server, it's missing obvious pairs like URL fetching or timezone listing beyond common names.