Skip to main content
Glama

web_tools_broken_links

[$x402 pago por llamada] Extrae hasta 30 links <a href> de una página y revisa cuáles responden con error (HEAD request a cada uno). Solo devuelve los links rotos, no la lista completa de links encontrados.

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": "<url>"
    },
    "name": "web_tools_broken_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the 30-link cap, the per-link HEAD request, and that it filters to only broken links, but omits what counts as 'error' (status codes vs. timeouts), failure handling for unreachable pages, rate limits, and the response shape.

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?

Two tight sentences; the core action is front-loaded after the bracketed payment tag, and no words are wasted. The payment note is relevant context rather than filler.

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 network-heavy tool with no annotations and no output schema, the definition covers purpose, mechanism, scope, and output filtering but leaves gaps around error definition, failure behavior, and return format that an agent would benefit from knowing.

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 50%: url is an undocumented bare string in the schema, and the description only implicitly frames it as 'a page' to scan. x_payment meaning is already covered by its schema description, so the description adds marginal value over structured fields.

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?

States a specific verb (extrae/revisa) and a concrete resource (links `<a href>` de una página), plus the exact mechanism and scope (hasta 30 links, HEAD request). It is clearly distinguishable from siblings like web_tools_metadata or net_tools_redirect_trace because it is specifically a broken-link checker.

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?

Implies the use case (finding broken links on a page) and clarifies output scope ('Solo devuelve los links rotos, no la lista completa'), but gives no explicit when/when-not or named alternatives among the many sibling web/net tools.

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.

Resources