Skip to main content
Glama

Etc/GMT clock

by io.github.sadri-dridi
OverviewDiscussionsAdmin

calc-eval

Evaluate a+b style arithmetic. Expression discarded.

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

D1.8/5.0
Behavior2/5

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals one trait—expression is discarded—but leaves ambiguous what the tool returns, whether it mutates anything, and how the 10 schema parameters are treated; the schema descriptions mention discard for some params, but the description does not clarify the overall behavior.

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

Conciseness2/5

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

The text is short and front-loaded, but for a 10-parameter tool with no annotations and no output schema, two sentences are under-specified rather than concise. 'Expression discarded' duplicates discard language that already appears throughout the parameter descriptions and adds no structural aid to the agent.

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

Completeness1/5

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

Given the tool's ambiguity, 10 optional parameters, no output schema, and no annotations, the description leaves the agent unable to construct a correct call: there is no expression field, no return contract, and no hint of what input produces a successful evaluation. The definition is materially incomplete.

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

Parameters1/5

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

Although schema coverage is 100%, the description adds no usable parameter semantics and in fact contradicts the schema by referring to an 'expression' that does not exist among the properties. The 10 parameters are left unexplained by the description, so the agent has no idea which (if any) carries the arithmetic expression.

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 names a verb and resource ('Evaluate a+b style arithmetic') but the input schema contains no expression parameter at all—instead it lists 10 unrelated optional fields such as url, city, feed, and json. A caller cannot map the stated purpose to any actual input, and no distinction is drawn from the many sibling shape-check tools.

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?

There is no guidance on when to invoke this tool rather than one of its ~29 siblings, and no exclusions or prerequisites are given. The only instruction-like statement ('Expression discarded') is a behavioral note, not a usage directive.

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

All Etc/GMT 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