Skip to main content
Glama

AI Visibility Audit

Check structured data for answer engines

check_schema_readiness
Read-onlyIdempotent

Read a page's JSON-LD structured data and report which entity signals an answer engine needs to describe the brand confidently (name, URL, logo, description, sameAs profiles, contact) are present or missing. Returns a shareable result page.

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": {
      "url": "<url>"
    },
    "name": "check_schema_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe website to check, e.g. https://example.com or example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value beyond that by scoping the read to JSON-LD specifically (implying other markup formats are not covered) and by disclosing that the tool produces a shareable result page, which matters because there is no output schema. It does not mention rate limits, auth, or behavior on pages with no structured data, hence 4 not 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?

Two sentences, front-loaded with what is read and what is reported, then the enumerable detail, then the return artifact. No filler, no restatement of the title.

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 one-parameter read-only check with full annotation coverage and no output schema, the description supplies the essential remaining information: what markup is inspected, which signals are graded, and that a shareable page comes back. Only lightly incomplete on what a missing-signal outcome looks like.

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?

There is a single required parameter with 100% schema description coverage, including a format example, so the schema carries the full burden. The description adds nothing about the URL parameter beyond what the schema already states, which is the baseline-3 case.

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 names a specific verb and resource — reads a page's JSON-LD structured data and reports which entity signals are present or missing — and enumerates the exact signals (name, URL, logo, description, sameAs, contact). That is far more specific than the title alone. It stops short of explicitly distinguishing itself from its siblings such as audit_ai_readiness or check_ai_crawler_access, so it lands at 4 rather than 5.

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 the framing in answer-engine terms — you run this when you want to know whether a brand's entity signals are discoverable — but there is no explicit when-to-use statement, no exclusion, and no pointer to a sibling tool for the adjacent audit tasks. Adequate context, no routing guidance.

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