Skip to main content
Glama

BRAINIAC Technical SEO Audits

Validate JSON-LD against schema.org

seo-technical_schema-org-validate
Read-onlyIdempotent

Check JSON-LD types and properties against a vendored schema.org Product/Offer vocabulary subset. Price $0.03 USDC. POST /api/v1/seo-technical/schema-org-validate. An unpaid call returns the x402 payment terms and does not run.

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": {
      "jsonld": "<jsonld>"
    },
    "name": "seo-technical_schema-org-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonldYesjsonld, value. Required.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/openWorld), the description discloses the commercial model ($0.03 USDC), the transport (POST /api/v1/...), and critically the failure mode: an unpaid call returns x402 payment terms and performs no validation. That is exactly the operational context an agent needs before invoking a paid endpoint.

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?

Three front-loaded sentences: purpose, price, endpoint, then the payment failure mode. Nothing is padded, though the endpoint path partially duplicates what the tool name and title already establish for an agent using the MCP layer directly.

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?

Output schema exists, so return values need not be explained, and the description covers purpose, cost, transport, and payment gating. The only residual gap is that it doesn't indicate whether validation covers required-property completeness vs type conformance only, which matters given the constrained vocabulary subset.

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?

Schema coverage is 100% with a single required `jsonld` parameter, so the schema already carries the burden and the baseline of 3 applies. The description adds only that the JSON-LD will be checked for types and properties against a Product/Offer subset, which slightly informs what the input should contain but adds no format or shape 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?

Specific verb (Check) + resource (JSON-LD types and properties) + the exact vocabulary being validated against (a vendored schema.org Product/Offer subset). The subset scoping also differentiates it from sibling validators like hreflang-validate and xml-sitemap-validate, which target different resources.

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?

The stated Product/Offer subset effectively tells an agent when the tool applies and implicitly when it does not (other schema.org types won't be covered), and the unpaid-call note warns what happens without payment. It stops short of explicitly naming an alternative or stating prerequisites for obtaining payment credentials, so it is clear but not fully routing.

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