Skip to main content
Glama

Asia/Kathmandu clock

by io.github.sadri-dridi
OverviewDiscussionsAdmin

tz-asia-kathmandu

Current local time in Asia/Kathmandu.

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

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the output (time). It does not mention that the tool accepts 10 optional parameters, that most are discarded, that it makes no network calls (based on schema hints like 'no disk access' and 'discarded after the shape check'), or any rate limits or side effects. The description adds no behavioral context beyond the obvious read-only nature of a time lookup.

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?

The description is a single clear sentence with zero filler. It immediately states the core purpose. There is no unnecessary introductory phrase or redundant detail. It is exemplary in conciseness, even if other dimensions suffer from its brevity.

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?

Despite having 10 parameters, no output schema, and no annotations, the description only provides a bare statement of output. It does not mention the return format (e.g., ISO 8601), the existence of optional parameters, or how the tool behaves when parameters are supplied. An agent cannot fully understand how to invoke the tool correctly without reading the schema closely, and even then, the description offers no guidance on expected results or edge cases.

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?

The input schema has 100% description coverage, so the schema already documents each parameter. The description adds no parameter-level meaning, such as clarifying that the 'zone' parameter can override the default timezone or that other parameters are ignored. According to the calibration rule, high schema coverage earns a baseline of 3, which is appropriate here.

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

Purpose4/5

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

The description 'Current local time in Asia/Kathmandu' clearly identifies the resource (Asia/Kathmandu) and the output (current local time). It distinguishes this tool from siblings like 'utc-time' and generic 'timezone' by fixing the zone. However, it is a noun phrase rather than an explicit verb, and it does not mention that the 'zone' parameter could override the timezone, which slightly reduces 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?

The description provides no guidance on when to use this tool versus the many timezone-related siblings. There is no mention of when to prefer this over 'timezone' or 'utc-time', nor any exclusions or alternative routing. An agent is left to infer usage solely from the name and description.

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

All Asia/Kathmandu 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