Skip to main content
Glama

net-web-media

json_ld_schema_validate

Extract and validate Schema.org JSON-LD blocks (from raw JSON-LD or HTML tags) for @context and @type completeness.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "json_ld_schema_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full transparency burden. It usefully narrows the meaning of 'validate' to @context and @type completeness (i.e., not a full Schema.org conformance check) and clarifies that HTML input is parsed for script tags, but says nothing about side effects, severity/reporting behavior, or failure modes.

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?

A single front-loaded sentence with no filler; the operation and the validation scope appear before the input-format aside. The nested parenthetical is slightly dense but still readable.

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

Completeness3/5

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

For a validator, the agent also needs to know what comes back (errors? missing @context vs missing @type? overall pass/fail), and no output schema exists to cover that. Combined with the undocumented filePath parameter and absent annotations, several call-relevant details are missing.

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?

Schema description coverage is 0% and the schema itself is bare (two untyped-in-prose string properties, neither required). The description explains the 'text' input's accepted shapes, which is genuine added value, but never mentions 'filePath' at all nor how the two inputs interact or which takes precedence.

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?

States specific verbs (extract, validate) against a specific resource (Schema.org JSON-LD blocks) and enumerates the two accepted input forms (raw JSON-LD or HTML script tags). The format specificity separates it from sibling validators like rss_atom_feed_validate and sitemap_xml_validate, though no sibling 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.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the resource name — an agent can infer it is for checking JSON-LD markup. There is no explicit when-to-use/when-not guidance, no statement of prerequisites, and no routing to alternatives for related tasks such as full Schema.org validation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources