Skip to main content
Glama

Validate HTML

validate_html
Read-onlyIdempotent

Validate supplied HTML markup or a single authorized public webpage URL with the Nu HTML Checker. Provide html for markup, or url for a live page. A standalone HTTP(S) URL in html is also fetched rather than treated as HTML. For combined SEO and JSON-LD checks on a live page, use audit_public_webpage.

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": "validate_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic webpage to fetch and validate as HTML; omit when providing html.
htmlNoRaw HTML markup or one standalone HTTP(S) webpage URL; omit when providing url.

Output Schema

NameRequiredDescriptionDefault
errorNo
messagesYes
overviewYes
truncatedYes
fetched_urlNo
total_messagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / html / description
      Previous value: -"Raw HTML markup supplied by the user; this is not a webpage URL."New value: +"Raw HTML markup or one standalone HTTP(S) webpage URL; omit when providing url."
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "Public webpage to fetch and validate as HTML; omit when providing html.",
      +  "format": "uri",
      +  "maxLength": 2048,
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "html"
      -]
    • addedOutput schema / properties / fetched_url
      Added value: +{
      +  "type": "string"
      +}
  2. Changed2 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"
  3. 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"
      +]
  4. Changed4 schema fields changed
    • addedInput schema / properties / html / description
      Added value: +"Raw HTML markup supplied by the user; this is not a webpage URL."
    • removedOutput schema / properties / errors
      Removed value: -{
      -  "items": {
      -    "additionalProperties": false,
      -    "properties": {
      -      "column": {
      -        "type": "number"
      -      },
      -      "line": {
      -        "type": "number"
      -      },
      -      "message": {
      -        "type": "string"
      -      },
      -      "type": {
      -        "enum": [
      -          "error",
      -          "warning",
      -          "info"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "type",
      -      "message"
      -    ],
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • addedOutput schema / properties / messages
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "column": {
      +        "type": "number"
      +      },
      +      "line": {
      +        "type": "number"
      +      },
      +      "message": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "enum": [
      +          "error",
      +          "warning",
      +          "info"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "message"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "errors",
      -  "total_messages",
      -  "truncated",
      -  "overview"
      -]New value: +[
      +  "messages",
      +  "total_messages",
      +  "truncated",
      +  "overview"
      +]
  5. Changed4 schema fields changed
    • 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"
      +}
    • addedOutput schema / properties / total_messages
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "errors"
      -]New value: +[
      +  "errors",
      +  "total_messages",
      +  "truncated",
      +  "overview"
      +]
  6. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already disclose read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds meaningful behavior beyond that: standalone HTTP(S) input in html is fetched and validated as a live page, not treated as markup. It does not discuss rate limits or fetch failures, so it stops short of a 5.

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?

Three tightly written sentences front-load the core operation, then cover the html/url split, the standalone-URL edge case, and the sibling alternative. Every sentence contributes a distinct decision-relevant fact.

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

Completeness5/5

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

With only two optional parameters, strong annotation coverage, and an output schema, the definition supplies everything an agent needs to choose this tool correctly: what it validates, how to supply each input form, what happens with URL-like html values, and when to prefer audit_public_webpage.

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

Parameters4/5

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

Schema coverage is 100%, but the description still adds value by clarifying the operational distinction between html (markup or standalone URL) and url (live page fetch) and that the two are alternatives. It reinforces rather than merely repeats the schema's omit-when-providing guidance.

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?

The description names a specific verb (validate), the exact resource (HTML markup or a live webpage), the engine (Nu HTML Checker), and explicitly distinguishes itself from audit_public_webpage. An agent can identify its purpose and scope without opening the schema.

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

Usage Guidelines5/5

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

It states exactly which parameter to use for markup (html) versus a live page (url), explains the standalone-URL-in-html fallback, and names audit_public_webpage as the alternative when combined SEO and JSON-LD checks are needed. The decision rule is explicit.

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