Skip to main content
Glama
Sign In
web-fetch-mcp

web-fetch-mcp

by KylinMountain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

compare_web

Compare content from multiple URLs. Submit a prompt with up to 20 URLs and your comparison instructions to receive a side-by-side analysis.

Instructions

Compare content from multiple URLs

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": {
      "prompt": "<prompt>"
    },
    "name": "compare_web"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesNatural language prompt containing URLs (up to 20) and comparison instructions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the high-level action with no details on input limits, output format, error behavior, or whether multiple URLs are required as opposed to optional.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It is appropriately concise for a simple tool, though it could be seen as under-specified in terms of what 'compare' entails.

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

Completeness3/5

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

For a tool with one parameter and no output schema, the description gives the essential purpose and the schema provides invocation details. However, it lacks usage context (e.g., what output to expect) and does not mention any constraints beyond what is in the schema.

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?

The schema description covers the single parameter well: 'Natural language prompt containing URLs (up to 20) and comparison instructions'. The tool description adds no additional parameter context, but since schema coverage is 100%, the baseline score of 3 applies.

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 a specific verb ('Compare') and resource ('content from multiple URLs'). It distinguishes itself from sibling tools (summarize_web, extract_web) by indicating a distinct action.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There is no mention of when comparison would be preferred over summarization or extraction, and no exclusion criteria are given.

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