Skip to main content
Glama

Validate a live page

validate_page
Read-onlyIdempotent

Fetch a public web page and audit its structured data: every JSON-LD block and type, the LocalBusiness markup's errors and warnings, LocalSchema embeds on the page and concrete recommendations. 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": {
      "url": "<url>"
    },
    "name": "validate_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) address, e.g. https://example.com/contact

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 readOnly, idempotent, and openWorld, so the bar is lower; the description still adds real value by confirming it performs an outbound network fetch of a live URL and requires no API key. It also discloses the shape of the audit output (errors, warnings, recommendations), which annotations cannot convey. It stops short of mentioning timeouts, rate limits, or behavior on unreachable/non-HTML pages.

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?

One front-loaded sentence with the action first and the enumerated outputs after; no filler. The colon-delimited list is dense but every item names a distinct returned artifact, so it earns its length.

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?

With no output schema, the description usefully enumerates what comes back and rules out an auth requirement, which is enough for a one-parameter read tool. Minor gaps remain around failure modes (unreachable page, non-HTML content, size limits) but nothing that would prevent a correct invocation.

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 well-described `url` parameter (public http(s) address, with example), so the schema carries the semantics. The description only reinforces that the target must be a public page; it adds no format or constraint detail beyond the schema, which is the expected baseline.

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+resource ('Fetch a public web page and audit its structured data') with the audited artifacts enumerated: JSON-LD blocks and types, LocalBusiness errors/warnings, LocalSchema embeds, and recommendations. The 'live page' framing implicitly but clearly separates it from the sibling validate_schema, which operates on a schema document rather than a fetched URL.

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 'Fetch a public web page and audit' and the 'No API key needed' note removes a common precondition, but the description never states when to prefer this over validate_schema or run_health_check. There are no explicit exclusions or alternative-routing guidance, leaving the agent to infer the choice from the tool name alone.

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