Skip to main content
Glama

Canonical URL check

bpj_canonical_link_check
Read-onlyIdempotent

Resolve a declared canonical link and check for cross-origin targets, fragments and tracking parameters.

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": {
      "page": "<page>",
      "declared": "<declared>"
    },
    "name": "bpj_canonical_link_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
declaredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds genuine behavioral content by enumerating the three conditions checked, but says nothing about what is returned (per-issue findings? boolean?), which matters since there is no output schema.

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?

A single well-formed sentence with the resolve action front-loaded and the checks enumerated as a compact list. No filler, though one more clause on the result shape would have been worth the words.

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?

A low-complexity, two-string, read-only check needs little, and the description covers the intent and the checks performed. With no output schema, however, the return contract and the two-parameter relationship are left undocumented, which is the remaining gap.

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% and the description only gestures at the 'declared' input. It never explains what the 'page' parameter is for or how the two URLs are compared (e.g. is the canonical resolved relative to page, and do fragments/tracking get stripped from which side?), so the two required strings remain semantically thin.

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?

Specific verb+resource: "Resolve a declared canonical link" plus three named checks (cross-origin targets, fragments, tracking parameters). An agent knows exactly what class of problem this detects, though it isn't differentiated by name from near-siblings like bpj_redirect_map_check or bpj_hreflang_reciprocity_check.

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 only implied: the framing of a 'declared canonical' against a 'current page' implies an SEO/audit context, but there is no explicit when-to-use statement, no prerequisite (e.g. HTML already parsed), and no named alternative for related link checks.

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.