Skip to main content
Glama

Validate schema markup

validate_schema
Read-onlyIdempotent

Validate existing LocalBusiness structured data: paste JSON-LD, a tag or a whole HTML page. Reports errors, missing recommended fields and best-practice warnings. No API key needed.

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": {
      "code": "<code>"
    },
    "name": "validate_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesJSON-LD text, a script tag, or full page HTML

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: what the output contains (errors, missing recommended fields, best-practice warnings) and that no API key is required — both are facts not present in the annotations.

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 short sentences: the action and scope first, the accepted input formats second, the results and auth note last. Nothing repeats the name or title, and every clause carries information.

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?

There is no output schema, and the description compensates by summarizing the three classes of findings returned. The one residual gap is scope ambiguity versus validate_page, which matters since both may accept HTML; the LocalBusiness qualifier helps but does not fully disambiguate.

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?

With one parameter at 100% schema coverage the schema already documents 'code'. The description still reinforces the accepted formats (JSON-LD text, script tag, full HTML page), which matches the schema semantics and reduces ambiguity about what counts as valid input. The 600k max length is left to the schema, which is appropriate.

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 opens with a specific verb and resource ('Validate existing LocalBusiness structured data') and immediately scopes the input types accepted. It implicitly separates itself from generate_schema by emphasizing 'existing' data, but never names validate_page, which is the closest sibling and whose overlap is left unresolved.

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 implied by 'Validate existing ... paste JSON-LD, a script tag or a whole HTML page', which tells an agent what to bring, but there is no explicit when-to-use/when-not statement and no named alternative such as validate_page or generate_schema. The agent must infer the routing itself.

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