AISeeWhy

compare_urls

Read-onlyIdempotent

Audit 2 or 3 URLs (yours and competitors') and compare them side by side: score, P1/P2/P3 counts, blocked crawlers, llms.txt, structured data, text without JavaScript. Needs an API key.

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": {
      "urls": "<urls>"
    },
    "name": "compare_urls"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes	2 or 3 page URLs or domains to compare; put your own page first.
`language`	No	Report language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 30 languages are supported.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 12, 2026

addedInput schema / properties / language / description

Added value: +"Report language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 30 languages are supported."

addedInput schema / properties / urls / description

Added value: +"2 or 3 page URLs or domains to compare; put your own page first."

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful operational context — the API-key requirement and the 2-or-3 cardinality constraint — but says nothing about cost, latency, or rate limits for an open-world, multi-page fetch.

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 sentence, front-loaded with the verb and scope, followed by a colon-delimited list of report contents. There is no filler and the auth requirement is tacked on as one short trailing clause.

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?

With an output schema present, the description need not describe return values, and it correctly focuses on scope, inputs, and prerequisites. The only gap is that it does not mention failure behavior when a URL is unreachable or a key is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds a genuine constraint not encoded in the schema: the array must contain 2 or 3 entries (the schema declares no minItems/maxItems). Language handling is fully covered by the schema itself.

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?

Specific verb (audit/compare) plus resource (2–3 URLs) plus an explicit enumeration of what is compared: score, P1/P2/P3 counts, blocked crawlers, llms.txt, structured data, and JS-free text. The '2 or 3 URLs' scope also implicitly separates it from the single-URL sibling audit_url.

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?

Establishes clear context (competitive side-by-side audit, your page first per schema) and a hard prerequisite (API key). It does not explicitly say when to prefer audit_url for a single page, so the routing to alternatives is left to inference.

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

All AISeeWhy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.