Skip to main content
Glama

RICOVANT AI Visibility Auditor

check_structured_data

Free public page JSON-LD and metadata check

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_structured_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP(S) website URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. 'Free' hints at no cost or auth requirement and 'public page' implies the URL is fetched server-side, but nothing states whether the call is read-only, whether it performs a live crawl, what happens on unreachable or non-HTML pages, or what the result contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no padding, so nothing is wasted, but it is telegraphic rather than front-loaded with the detail an agent needs. Brevity here reflects under-specification more than disciplined concision.

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

Completeness2/5

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

For a tool that fetches an external URL with no annotations and no output schema, the description should say what is returned and how failures surface. Neither is covered, leaving an agent unable to predict results or error behavior before calling.

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 one parameter at 100% schema coverage, the schema already defines the URL as a public HTTP(S) URI. The description's 'public page' wording reinforces that constraint but adds no format, normalization, or validation detail beyond the structured field.

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

Purpose3/5

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

The fragment names specific resources (JSON-LD, page metadata) and an action (check), which does distinguish it loosely from check_ai_crawlers and audit_ai_visibility. But it is a noun phrase without a verb subject, and 'check' is vague about what is actually verified or produced, so an agent gets the topic but not the operation.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of the sibling tools. The word 'public' implicitly limits scope to publicly reachable pages, but nothing says when an agent should reach for this versus an AI-visibility audit.

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