Check whether a body is valid JSON. The body is discarded.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | HTTPS URL to normalize or cite | |
| host | No | Public hostname | |
| json | No | JSON text to validate; discarded after the check | |
| zone | No | IANA timezone name |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden, and it does disclose a meaningful trait: 'The body is discarded' signals that the JSON input is not retained. However, it fails to disclose what happens on success or failure—whether the tool returns a boolean, an error, or something else—so key behavioral context is missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single two-clause sentence with zero filler: it front-loads the purpose ('Check whether a body is valid JSON') and immediately follows with a behavioral consequence ('The body is discarded'). Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema, no annotations, and a 4-parameter schema with three parameters (url, host, zone) unrelated to the stated purpose. The description does not specify the return behavior, does not flag the extraneous parameters, and does not fully equip an agent to invoke or interpret the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the 'json' parameter description even repeats the discard behavior, so the description adds no extra parameter meaning. The main weakness is that the description does not connect 'body' to the 'json' parameter or explain why url, host, and zone appear in a JSON-validation tool, leaving an obvious ambiguity unresolved.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Check whether a body is valid JSON.' This clearly distinguishes the tool from the sibling tools oriented at URLs, hosts, and timezones. However, 'body' is slightly ambiguous because the schema's relevant parameter is named 'json,' and no sibling or relationship is named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use validate-json versus alternatives, nor any exclusions or conditions. The sibling tools are not mentioned, and the only additional sentence ('The body is discarded') describes behavior rather than usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The time-related tools (epoch-ms, utc-time, timezone, iana-zones) are distinguishable, but several URL tools overlap in input and output: citation and normalize-url both expose host/URL components, and compatibility is vague about what it classifies. An agent could misselect between the URL inspection tools despite helpful descriptions.
Names are mostly lowercase with hyphens, but there is no consistent grammatical pattern: noun phrases like epoch-ms, utc-time, and status-catalog mix with imperative verbs like inspect-robots, normalize-url, and validate-json. This inconsistency makes the naming style readable but unpredictable.
Eleven tools is a reasonable count on its own, but the set is not tightly scoped to the server's apparent identity of Unix epoch milliseconds; it mixes time, URL, robots, status code, and JSON utilities. This feels like a general utility grab-bag rather than a focused toolset.
For the time domain implied by the server name, there are no epoch-to-date conversions, formatting helpers, or timezone offset details, leaving obvious gaps. The URL/request utilities are similarly fragmentary, covering shape and status but not full content retrieval or more useful metadata, so the surface feels incomplete for any single stated purpose.