Skip to main content
Glama

Current UTC hour from unix seconds

by io.github.sadri-dridi
OverviewDiscussionsAdmin

unix-hr

Current UTC hour from unix seconds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoGit ref name; discarded after the shape check
urlNoHTTPS URL to normalize or cite
cityNoCity name for a public weather hint; discarded after the call
feedNoPublic RSS or Atom URL; titles discarded
hostNoPublic hostname
jsonNoJSON text to validate; discarded after the check
pathNoFile path to check; no disk access
zoneNoIANA timezone name
queryNoSearch text; discarded after the length check
websiteNoPublic https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / website
      Added value: +{
+  "description": "Public https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.",
+  "type": "string"
+}
  2. First observed

TDQS

C2.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Current UTC hour from unix seconds' and does not disclose that most parameters are discarded, that the tool performs multiple unrelated checks, or what side effects or limitations exist. The schema descriptions mention 'discarded after the shape check' for several params, but the main description does not synthesize this behavior. The tool appears to be a multi-purpose validator/checker disguised as a time tool, which is misleading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one sentence), which is concise, but it is under-specified. It does not front-load the key behavioral information (that it is a multi-purpose utility with many discardable parameters). The brevity is not effective because it omits critical context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 10 parameters, no output schema, and no annotations, the description is severely incomplete. An agent cannot determine what the tool actually does with all these parameters, what the return value looks like, or when to use it. The description 'Current UTC hour from unix seconds' is insufficient for a tool with this complexity and parameter count.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter has a description in the schema. However, the main description does not explain how these parameters relate to the tool's stated purpose of returning the current UTC hour. The schema descriptions add some meaning (e.g., 'discarded after the shape check'), but the overall semantics are confusing because the parameters seem unrelated to the tool's name and description. Baseline 3 is appropriate since the schema covers all parameters, but the description adds no integrative value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Current UTC hour from unix seconds' states a verb and resource, but the tool name 'unix-hr' and the 10 unrelated parameters (ref, url, city, feed, host, json, path, zone, query, website) make the actual purpose extremely unclear. It appears to be a multi-purpose utility that returns the current UTC hour, but the description does not explain why it accepts all these parameters or how they relate to the output. The description is too terse to distinguish it from siblings like utc-time or timezone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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, timezone, or iana-zones. The description does not mention any conditions, exclusions, or alternative tools. The presence of 10 parameters with no explanation of their role leaves the agent without any usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Current UTC hour from unix seconds toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources