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 conveys that the tool returns the current time, but it does not disclose output format, error behavior, or the fact that url/host/json parameters appear irrelevant to the tool's purpose, which can mislead an agent.
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, front-loaded sentence with no wasted words. It is concise, though arguably too terse for a tool with a mismatched four-parameter schema.
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 tool has four optional parameters, no output schema, and no annotations, so the description must compensate. It does not specify which parameter to pass, what output shape to expect, or how the current time is formatted, leaving an agent with significant ambiguity.
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?
Although schema coverage is 100%, most parameters (url, host, json) have descriptions that point to unrelated behaviors like normalization, citation, and validation. The description mentions 'named IANA timezone' and the zone parameter is described as 'IANA timezone name', but the description fails to clarify that zone is the only meaningful parameter.
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 verb+resource: returning the current time for a named IANA timezone. It is clear on its own, though it does not distinguish this tool from siblings.
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?
There is no guidance on when to use this tool or how it relates to sibling tools. The description also fails to indicate that the 'zone' parameter is the relevant one, especially given that the schema exposes unrelated parameters.
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.
Several tools have overlapping concerns: citation, normalize-url, and domain-shape all analyze URLs/hostnames, while timezone, utc-time, and iana-zones all relate to time. The purpose of compatibility is vague and could be confused with the URL inspection tools. Only a few tools like slug-ok and validate-json are clearly distinct.
All names use lowercase hyphenation, which is consistent, but the pattern is mixed: some are verb phrases (normalize-url, inspect-robots, validate-json), while others are bare nouns (citation, compatibility, timezone). There is no unified verb_noun convention, though the names remain readable.
Eleven tools is not an unreasonable count by itself, but the tool set is unfocused for a server named 'Slug character check.' Most tools address unrelated concerns such as time, URLs, HTTP status, and JSON, making the collection feel padded rather than purpose-built.
The server lacks a coherent domain: slug checking has only one thin tool, URL utilities have no encoding/decoding or query-param handling, and time utilities lack conversions or formatting options. For any single stated purpose, the surface has significant gaps and no end-to-end workflow.