Skip to main content
Glama

BRAINIAC Technical SEO Audits

Validate an hreflang cluster

seo-technical_hreflang-validate
Read-onlyIdempotent

Check BCP 47 codes against the IANA subtag registry and reciprocal return tags across caller-supplied page alternates. Price $0.03 USDC. POST /api/v1/seo-technical/hreflang-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": {
      "pages": "<pages>"
    },
    "name": "seo-technical_hreflang-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYespages, array. Required.

Output Schema

NameRequiredDescriptionDefault
errorsNoerrors. Array.
sourcesNosources. Array.
clustersNoclusters. Number.
warningsNowarnings. Array.
limitationsNolimitations. Array.
normalisationNonormalisation. Object.

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 readOnly, idempotent, and non-destructive, but the description adds material behavior the annotations do not: a $0.03 USDC charge, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms and does not run. That last point is exactly the kind of failure mode an agent needs before calling. It leaves out error semantics beyond payment, but the added context is substantial.

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?

Four short sentences, front-loaded with the validation semantics, followed by price, endpoint, and the unpaid-call caveat in descending order of importance. No filler, though the raw endpoint string is low-value for an agent and slightly dilutes the opening.

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?

An output schema exists, so return-value explanation is not needed, and the description covers what is checked, what input is expected, and the payment gating. Remaining gaps are modest: behavior on malformed clusters, partial failure, and whether canonical values are validated are unstated, but an agent has enough to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single 'pages' parameter, so the structural baseline is 3. The description still adds meaning by clarifying that the alternates are caller-supplied rather than crawled, which changes how the agent must build the payload. It does not add detail about canonical handling or how reciprocal return tags are evaluated, so a 4 rather than 5.

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?

States a specific verb-and-resource pair: checks BCP 47 codes against the IANA subtag registry and reciprocal return tags across page alternates. That is far more precise than the title and an agent can tell it is the hreflang validator rather than the sitemap, canonical, or schema-org validators. It does not explicitly distinguish itself from those siblings, so it stops short of a 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?

Phrasing like 'caller-supplied page alternates' implies the caller must assemble the cluster and pass it in, which is useful implied usage. But there is no explicit when-to-use or when-not guidance, no prerequisites, and no pointer to what to do if the agent only has URLs rather than collected alternates.

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