Skip to main content
Glama

Validate JSON-LD syntax

validate_schema_markup
Read-onlyIdempotent

Use this for a focused JSON-LD syntax check of supplied HTML. It parses JSON only and does not validate Schema.org vocabulary semantics.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "html": "<html>"
    },
    "name": "validate_schema_markup"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesRaw HTML markup supplied by the user; this is not a webpage URL.

Output Schema

NameRequiredDescriptionDefault
errorNo
issuesYes
overviewYes
truncatedYes
total_issuesYes
blocks_checkedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / properties / issues / items / properties / code
      Added value: +{
      +  "description": "Stable machine-readable audit rule identifier.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / issues / items / required
      Previous value: -[
      -  "severity",
      -  "category",
      -  "message"
      -]New value: +[
      +  "code",
      +  "severity",
      +  "category",
      +  "message"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / overview / properties / kind / enum
      Previous value: -[
      -  "html",
      -  "css",
      -  "seo",
      -  "schema",
      -  "links",
      -  "report"
      -]New value: +[
      +  "html",
      +  "css",
      +  "seo",
      +  "schema",
      +  "links",
      +  "report",
      +  "site"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / html / description
      Added value: +"Raw HTML markup supplied by the user; this is not a webpage URL."
  4. Changed4 schema fields changed
    • addedOutput schema / properties / blocks_checked
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / error
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / overview
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "counts": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "key": {
      +            "type": "string"
      +          },
      +          "label": {
      +            "type": "string"
      +          },
      +          "tone": {
      +            "enum": [
      +              "error",
      +              "warning",
      +              "info",
      +              "success"
      +            ],
      +            "type": "string"
      +          },
      +          "value": {
      +            "maximum": 9007199254740991,
      +            "minimum": 0,
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "key",
      +          "label",
      +          "value",
      +          "tone"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "detail": {
      +      "type": "string"
      +    },
      +    "headline": {
      +      "type": "string"
      +    },
      +    "kind": {
      +      "enum": [
      +        "html",
      +        "css",
      +        "seo",
      +        "schema",
      +        "links",
      +        "report"
      +      ],
      +      "type": "string"
      +    },
      +    "next_action": {
      +      "type": "string"
      +    },
      +    "shown": {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "status": {
      +      "enum": [
      +        "passed",
      +        "needs_attention",
      +        "partial",
      +        "failed",
      +        "not_applicable"
      +      ],
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "total": {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "kind",
      +    "status",
      +    "title",
      +    "headline",
      +    "detail",
      +    "total",
      +    "shown",
      +    "truncated",
      +    "counts"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "issues",
      -  "total_issues",
      -  "truncated"
      -]New value: +[
      +  "issues",
      +  "total_issues",
      +  "truncated",
      +  "overview",
      +  "blocks_checked"
      +]
  5. Changed3 schema fields changed
    • addedOutput schema / properties / total_issues
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "issues"
      -]New value: +[
      +  "issues",
      +  "total_issues",
      +  "truncated"
      +]
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the bar is lower. The description usefully adds a scope boundary — it parses JSON only and stops short of vocabulary/semantic validation — telling the agent what a 'pass' does and does not mean. It does not describe error reporting for malformed JSON, though the output schema likely covers the response shape.

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?

Two sentences, zero filler, with the capability stated first and the limitation second. Both sentences carry distinct information an agent needs.

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

Completeness4/5

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

For a simple single-parameter validation tool with a published output schema and full annotation coverage, the description supplies the essential scope framing. Return-value details are correctly left to the output schema, leaving only minor unstated items such as behavior on malformed input.

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

Parameters3/5

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

With a single parameter at 100% schema description coverage, the schema already documents that 'html' is raw markup rather than a URL. The description adds no format, size, or encoding detail beyond that, so it earns the baseline rather than more.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: a syntax check of JSON-LD embedded in HTML. The word 'focused' plus 'JSON-LD' distinguishes it from sibling HTML/CSS validators without naming them, so an agent can select it directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives a clear condition for use ('JSON-LD syntax check of supplied HTML') and an explicit exclusion ('does not validate Schema.org vocabulary semantics'), which prevents misuse for semantic auditing. No sibling alternative is named for that out-of-scope case, so it falls short of a 5.

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