Skip to main content
Glama

Asia/Dubai clock

by io.github.sadri-dridi
OverviewAdmin

validate-json

Check whether a body is valid JSON. The body is 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

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.7/5.0
Behavior2/5

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

The statement 'The body is discarded' hints at a lack of side effects, but it does not clarify whether the tool returns a result, modifies any state, or has other behavioral implications. With no annotations, this is insufficient.

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 concise, consisting of two short sentences. It front-loads the primary action, but the second sentence adds a minor detail that could be omitted without losing core meaning.

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?

With four parameters and no output schema, the description is incomplete. It does not specify what happens after validation, the meaning of 'valid', or how the parameters are used. The ambiguous term 'body' compounds the incompleteness.

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?

The tool description does not connect the parameters (url, host, json, timezone) to the stated purpose. While the schema provides individual descriptions, the relationship between these parameters and 'checking a body' is not explained, leaving the mapping unclear.

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 clearly states the action ('check whether a body is valid JSON') and distinguishes it from sibling tools like normalize-url and timezone. However, 'body' is ambiguous as it could refer to an HTTP request body or a JSON string parameter, so it is not perfectly precise.

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 given on when to use this tool versus alternatives, nor are any conditions or prerequisites mentioned. The description only covers what it does, not when to use it.

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

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