Skip to main content
Glama

America/Sao_Paulo clock

by io.github.sadri-dridi
OverviewAdmin

utc-time

Current UTC timestamp.

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
+  "description": "City name for a public weather hint; discarded after the call",
+  "type": "string"
+}
    • addedInput schema / properties / feed
      Added value: +{
+  "description": "Public RSS or Atom URL; titles discarded",
+  "type": "string"
+}
    • addedInput schema / properties / path
      Added value: +{
+  "description": "File path to check; no disk access",
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Search text; discarded after the length check",
+  "type": "string"
+}
    • addedInput schema / properties / ref
      Added value: +{
+  "description": "Git ref name; discarded after the shape check",
+  "type": "string"
+}
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral burden. It only says 'Current UTC timestamp,' which is minimal. It does not disclose whether parameters are ignored, whether the tool is read-only, or what the response structure looks like. This is a significant gap for a tool with a mismatched schema.

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

Conciseness4/5

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

The description is a single, short sentence with no filler. It is efficient and front-loaded, but the brevity sacrifices necessary 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?

For a simple tool, the description might suffice if the schema were aligned, but here the schema introduces four unrelated optional parameters with no explanation. The tool lacks an output schema, and the description does not clarify return values or parameter usage, making it incomplete for an agent to call it confidently.

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

Parameters2/5

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

Although the schema provides descriptions for each parameter, the tool description does not connect them to the tool's purpose. The parameters (url, host, json, zone) appear irrelevant to fetching a UTC timestamp, and the description offers no explanation for their presence, leaving the agent confused about how to invoke the tool correctly.

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

Purpose3/5

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

The description states the tool returns the current UTC timestamp, which is a clear verb+resource. However, it is vague about the output format (e.g., ISO string, Unix epoch) and does not explain why the input schema contains four unrelated parameters (url, host, json, zone). This ambiguity prevents full clarity.

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 siblings like timezone, iana-zones, or tz-america-sao-paulo. The description does not mention that this is for fetching current UTC time as opposed to conversions or zone lookups, leaving the agent to infer usage.

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

All America/Sao_Paulo clock toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources