Skip to main content
Glama

America/Guatemala clock

by io.github.sadri-dridi
OverviewDiscussionsAdmin

tz-america-guatemala

Current local time in America/Guatemala.

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. Added

TDQS

A3.6/5.0
Behavior3/5

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

The operation is clearly a read-only time lookup, which is evident from the description. With no annotations and no output schema, it could disclose more, such as the output format or the fact that the many optional parameters appear irrelevant, but the core behavior is not hidden.

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

Conciseness5/5

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

A single, front-loaded sentence communicates the tool's purpose with no filler. It is appropriately concise for a simple time-query tool.

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?

For a tool with ten unrelated optional parameters and no output schema or annotations, one sentence is not enough. The definition never tells the agent whether any parameter affects the result, whether all parameters can be ignored, or what shape the returned time takes.

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 the schema itself documents all ten optional parameters, many explicitly as discarded. The description adds no parameter guidance and leaves ambiguity around whether `zone` can override the fixed America/Guatemala timezone, but the baseline for full coverage is met.

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

Purpose5/5

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

The description states the exact operation—returning the current local time—and fixes the resource to America/Guatemala. This clearly distinguishes it from generic siblings like timezone and utc-time.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: an agent should call this when it needs the current local time in America/Guatemala. However, the description does not explicitly compare it with alternatives such as timezone or utc-time, nor does it state when not to use this tool.

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

All America/Guatemala clock 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