Skip to main content
Glama
Sign In
MWIE MCP Server

MWIE MCP Server

by tmolavi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

compare_pages

Compare multiple competitor pages side by side to assess SEO and generative-engine (GEO) readiness, helping identify content and technical gaps.

Instructions

Compare multiple competitor pages side-by-side on SEO and GEO readiness.

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_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It reveals only the comparison scope (SEO/GEO readiness across pages) and omits operational details such as URL count limits, synchronization versus asynchronous behavior, authentication requirements, rate limits, or whether it fetches pages itself.

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 a single front-loaded sentence with no filler; it communicates the action and comparison dimensions immediately. The brevity is appropriate for the sentence, even though more detail is needed elsewhere.

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

Completeness2/5

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

Although an output schema exists and reduces the need to explain return values, the tool has no annotations and only a minimally documented input schema. The description leaves important call-context gaps: how many pages can be compared, whether the call is synchronous, and what 'SEO and GEO readiness' entails.

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 'urls' parameter. The description adds that the URLs should be multiple competitor pages, but it does not specify URL format, minimum or maximum count, or any other constraint that would help an agent populate the array correctly.

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 gives a specific verb ('Compare'), a clear resource ('multiple competitor pages'), and the comparison dimensions ('SEO and GEO readiness'). It implies cross-page comparison rather than single-page analysis, but it does not explicitly name or distinguish itself from sibling tools such as analyze_seo or analyze_geo.

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?

The phrase 'Compare multiple competitor pages side-by-side' implies the tool is for cross-page competitive comparison. However, it offers no explicit when-to-use or when-not-to-use guidance and does not name alternatives, leaving the agent to infer that analyze_seo and analyze_geo are for single-page checks.

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