Skip to main content
Glama
OrtaMarco

seo-geo-mcp-server

by OrtaMarco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Canonical Host Check

canonical_host_check
Read-onlyIdempotent

Checks all four http/https and apex/www variants of a domain to confirm they redirect to a single canonical URL, identifying redirect types, HTTPS enforcement, and unreachable variants.

Instructions

Fetch all four host/scheme variants of a domain — http/https × apex/www — and confirm they converge on a single canonical URL. Divergence is the classic cause of a homepage competing with itself in the index.

Also reports whether plain HTTP is upgraded to HTTPS, whether canonicalisation uses permanent (301/308) rather than temporary (302/307) redirects, and which variants do not serve content at all.

Args:

  • site (string): a domain such as 'example.com' (www and scheme are ignored).

  • response_format ('markdown' | 'json'): output format (default 'markdown').

Returns: { domain, variants[{variant, reachable, status, final_url, hop_count, redirect_statuses[]}], canonical_url, converges, distinct_endpoints[], forces_https, score, grade, findings[] }.

Example: "Do all versions of example.com redirect to one URL?" -> canonical_host_check(site="example.com").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesSite domain or any URL on it, e.g. 'example.com'. Only the origin is used.
response_formatNoOutput format: 'markdown' for a human-readable summary (default) or 'json' for the full structured payload.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gradeYes
scoreYes
domainYes
findingsYes
variantsYes
convergesYes
forces_httpsYes
canonical_urlYes
distinct_endpointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses useful behavioral details: it reports whether HTTP is upgraded to HTTPS, whether redirects are permanent versus temporary, and which variants do not serve content. This gives the agent a concrete picture of what the tool will compute.

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?

The description is well organized: purpose, additional behavior, Args, Returns, and Example. It is front-loaded with the core function, and every section earns its place without redundant filler.

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

Completeness5/5

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

With a full output schema, complete parameter documentation, behavioral details, and an example call, the description gives an agent everything needed to select and invoke the tool correctly. No important operational context is missing.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds meaning by explaining that 'www and scheme are ignored' for the site parameter, specifying the default for response_format, and showing a natural-language-to-API example. This goes beyond the schema's property descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: fetch all four host/scheme variants and confirm they converge on a single canonical URL. This clearly distinguishes the tool from siblings like redirect_trace, which traces a single redirect path rather than comparing variants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context by noting divergence is the classic cause of a homepage competing with itself in the index, and it gives an example query. It does not explicitly name alternative tools or state when not to use it, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools