Skip to main content
Glama

Hreflang reciprocal link check

bpj_hreflang_reciprocity_check
Read-onlyIdempotent

Find missing self-references, missing return links and conflicting language targets.

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": {
      "mapping": "<mapping>"
    },
    "name": "bpj_hreflang_reciprocity_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
mappingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is well covered and the bar is lower. The description adds value by naming the three failure categories the tool reports, which is real behavioral information about what a run surfaces. It says nothing about ordering, severity, or how results are presented, so it goes no further.

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 compact sentence with zero filler, front-loaded on the outcomes the tool produces. It is arguably under-sized for the job rather than padded, but nothing is wasted.

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 read-only single-parameter check with no output schema, the description covers what is detected but not how the input must be assembled or what form the findings take. Annotations carry the safety profile, and the schema title hints at input format, so it is adequate but leaves an agent guessing on invocation details.

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

Parameters2/5

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

The single required parameter 'mapping' is never mentioned in the description, and schema description coverage is 0%. The schema's property title ('Page URL | language tag | alternate URL per line') does encode the expected line format, which mitigates the gap somewhat, but the description contributes no meaning about the required pipe-delimited structure, ordering, or the 8000-character limit.

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 ('Find') and enumerates three concrete defect classes it detects: missing self-references, missing return links, and conflicting language targets. The resource (hreflang) is only implied via the tool name and title, not the description text, and no sibling is distinguished, so it falls 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 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 when-not-to-use, and no named alternative among the many link-checking siblings (e.g., bpj_canonical_link_check, bpj_redirect_map_check). An agent must infer from the name alone that this is the hreflang-specific audit rather than a general link check.

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.