Skip to main content
Glama

GEO & SEO Readiness (Lite)

compare_two_domains_readiness

Read-onlyIdempotent

Run parallel deterministic non-JS AI search & SEO readiness probes on two public URLs (url_a vs url_b) and return a structured side-by-side gap table.

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": {
      "url_a": "<url_a>",
      "url_b": "<url_b>"
    },
    "name": "compare_two_domains_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_aYesFirst public URL (e.g., your site https://example.com).
url_bYesSecond public URL (e.g., competitor https://cloudflare.com).

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 cover safety (readOnly, idempotent, non-destructive, openWorld), so the description earns credit for adding beyond them: 'deterministic' signals repeatable results, 'non-JS' warns that JavaScript-rendered content is not evaluated, and 'public URLs' implies no auth is needed. It does not mention rate limits, failure handling, or per-URL error semantics when one site is unreachable.

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?

A single dense sentence with the action, the inputs, and the output front-loaded; no filler or restated title.

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?

For a two-parameter read-only comparison with no output schema, the description gives enough — the probe type, the deterministic non-JS caveat, and the shape of the result. A note on partial failures or score interpretation would round it out.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented, including the 'your site' vs 'competitor' framing. The description adds only the ordering notion in 'url_a vs url_b', which is marginal value over the schema — baseline 3.

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 action (run parallel readiness probes) on a specific resource (two public URLs) and names the return artifact (side-by-side gap table). The comparative single-vs-pair distinction from audit_ai_search_readiness is implied by 'two public URLs' rather than stated, 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?

Usage is implied by the word 'compare' and the url_a-as-your-site / url_b-as-competitor framing in the schema. There is no explicit when-to-use, when-not-to-use, or pointer to the single-URL sibling for one-sided 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.