Skip to main content
Glama

Caelara Labs SEO & GEO Readiness

hreflang_validator

Validate hreflang annotations: codes, x-default, self-reference and optional return links

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": "hreflang_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL
check_return_linksNoVerify reciprocal links on up to 5 alternates (true/false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the concrete checks performed, which is real behavioral content beyond the name. However, it never says the tool fetches the remote page at 'url' (network access, latency, possible failures), nor does it describe the result shape despite there being no output schema. It also leaves the 'up to 5 alternates' scope for return-link checking to the schema rather than stating the limit itself.

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?

One compact clause, front-loaded with the verb and resource, with the enumerated checks as the payload. No filler or redundancy.

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

Completeness3/5

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

For a simple two-parameter validator this covers the 'what is checked' question adequately. It is incomplete on two fronts relative to the absence of an output schema: what the response contains (pass/fail per tag, error list) and whether the call performs a live fetch of the target URL.

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%, so both parameters are already documented, and the description's 'optional return links' only loosely echoes check_return_links. No added syntax, format, or defaulting guidance beyond what the schema provides, so the baseline 3 applies.

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?

A specific verb ('Validate') plus a specific resource ('hreflang annotations'), followed by an enumeration of the checks performed (codes, x-default, self-reference, return links). This is enough to distinguish it from siblings like schema_org_validator or broken_link_scanner, though it never names an alternative explicitly.

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 or when-not-to-use guidance, no prerequisites, and no mention of alternatives. A reader can infer it is the right tool for auditing hreflang tags, but nothing tells them when to prefer it over the composite or other SEO validators, or when return-link checking is worth enabling.

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