Skip to main content
Glama
yantrix-ai

@praveen030686/data-apis-mcp

Compare Two Pages

web_extract_compare
Read-onlyIdempotent

Analyze and compare content from two web pages using AI to identify similarities and differences.

Instructions

Compare content of two web pages with AI analysis of similarities and differences. Costs $0.08 USDC per request via x402 on Base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
url1YesFirst URL to compare
url2YesSecond URL to compare

Implementation Reference

  • The handler function for 'web_extract_compare' that calls the extract compare API.
    async ({ url1, url2 }) => {
      const data = await apiPost(`${WEB_EXTRACT_API}/api/v1/extract/compare`, { url1, url2 });
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • src/index.ts:387-403 (registration)
    Registration of the 'web_extract_compare' tool, including its schema and description.
    server.registerTool(
      "web_extract_compare",
      {
        title: "Compare Two Pages",
        description: `Compare content of two web pages with AI analysis of similarities and differences.
    Costs $0.08 USDC per request via x402 on Base.`,
        inputSchema: {
          url1: z.string().url().describe("First URL to compare"),
          url2: z.string().url().describe("Second URL to compare"),
        },
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      },
      async ({ url1, url2 }) => {
        const data = await apiPost(`${WEB_EXTRACT_API}/api/v1/extract/compare`, { url1, url2 });
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
Behavior4/5

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

Annotations already indicate read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable context beyond this by disclosing the cost ($0.08 USDC per request via x402 on Base), which is critical for usage decisions. It doesn't contradict annotations, as 'compare' aligns with read-only, and no other behavioral traits like rate limits or auth needs are mentioned.

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 appropriately sized with two sentences: the first states the core functionality, and the second adds critical cost information. It is front-loaded with the main purpose and has zero wasted words, making it highly efficient and easy to parse.

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?

Given the tool's moderate complexity (AI analysis of two pages), rich annotations (covering safety and behavior), and no output schema, the description is mostly complete. It covers purpose and cost, but could benefit from mentioning output format or analysis scope. However, with annotations providing behavioral context, it is largely adequate for agent use.

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 description coverage is 100%, with both parameters (url1 and url2) well-documented in the schema. The description does not add any meaning beyond the schema, such as format details or constraints, so it meets the baseline of 3 for high schema coverage without extra param info.

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 clearly states the tool's purpose with specific verbs ('compare content of two web pages') and resources ('web pages'), and distinguishes it from siblings like web_extract_ai_summary or web_extract_text by specifying AI analysis of similarities and differences. It goes beyond a tautology of the name/title.

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 description implies usage for comparing web pages with AI analysis, but provides no explicit guidance on when to use this tool versus alternatives like web_extract_structured or web_extract_batch. It mentions a cost, which hints at resource considerations, but lacks clear when/when-not directives or named alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yantrix-ai/x402-apis-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server