Skip to main content
Glama

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

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

The description mentions that 'the body is discarded,' which is a side-effect statement, but it fails to clarify whether the tool performs a network request (given the url/host parameters) or operates on the provided json parameter. The actual behavior is under-specified, and no annotations are available to supplement.

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 extremely concise, consisting of a single sentence with no unnecessary words or repetition. It directly states the core function and a key side-effect (discarding the body), making it easy to parse quickly.

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?

The description is critically incomplete. It does not explain the role of the url, host, and zone parameters, nor does it specify the expected output or behavior of the validation (e.g., return value, success/failure indication). Given the parameter complexity, the description fails to provide essential context for correct usage.

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 each parameter has a description, they are incoherent with the tool's stated purpose. The 'json' parameter aligns with validation, but 'url', 'host', and 'zone' appear unrelated to JSON validation and are not explained in the tool description. The description's reference to 'body' does not map clearly to any parameter, creating confusion.

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 identifies the resource (JSON). The name 'validate-json' reinforces this purpose. However, the term 'body' is ambiguous, and it does not explicitly distinguish this tool from potential alternatives, though no sibling tool directly competes.

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 other available tools. The description does not mention any prerequisites, scenarios, or alternative tools, leaving the agent without clear direction on when to invoke this functionality.

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

All America/Mexico_City 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