Skip to main content
Glama

Hreflang cluster markup

bpj_hreflang_html_cluster
Read-onlyIdempotent

Validate language tags, reject duplicate locales and generate hreflang alternate 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": {
      "locales": "<locales>"
    },
    "name": "bpj_hreflang_html_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
localesYes

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 a closed-world scope, so safety is fully covered. The description adds one genuinely new behavioral fact — duplicate locales are rejected rather than silently deduplicated — but says nothing about what the generated links look like, where they are returned, or whether validation failures abort the whole response or are reported per line.

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 sentence, three clauses, no filler, and the validate-then-generate order is front-loaded and easy to parse. It is efficient but arguably too terse for a tool whose only input format is undocumented.

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?

With no output schema, the description should clarify the shape of the generated hreflang links, yet it only says they are 'generated'. Combined with an undocumented pipe-delimited input and no stated failure behavior, the definition is adequate for a simple text-in tool but leaves real gaps an agent would hit on first use.

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?

Schema description coverage is 0% for the single required parameter, so the description carries the burden of explaining the input format and does not do so. The only format hint ('Language|URL, one version per line') lives in the schema title, and nothing explains accepted language-tag syntax, whether URLs must be absolute, or what counts as a duplicate locale.

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?

The description states three concrete actions — validate language tags, reject duplicate locales, generate hreflang alternate links — against a named resource, so the agent knows this builds cluster markup rather than auditing existing markup like the reciprocity sibling. It stops short of explicitly contrasting with bpj_hreflang_reciprocity_check, but the verb set is specific enough to distinguish the two.

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 statement of when to reach for this instead of the reciprocity checker, and no prerequisites (e.g. that all alternates for a page should be submitted together). The agent must infer the context entirely from the purpose sentence.

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.