Skip to main content
Glama

LinkVet

Find broken links on a page

broken_links
Read-onlyIdempotent

Fetch a page, collect its unique outbound/internal links and check each one (in parallel) for 404s, timeouts and connection errors. Returns broken links with their anchor text and the status of every link checked (up to 25 per call).

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": "broken_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage to audit
limitNoMax unique links to check (default 20, max 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, open world), and the description still adds real behavioral detail: checks run in parallel, failure classes covered are 404s, timeouts and connection errors, and throughput is capped at 25 checks per call. It does not mention redirect handling or whether external requests respect robots, which are the remaining open questions for an open-world fetcher.

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 dense sentence that front-loads the action sequence and closes with the return shape and the hard cap. No filler and nothing a reader would have to scroll for.

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 no output schema, the description carries the return burden and does so: broken links plus anchor text plus the status of every link checked. The cap on results is disclosed. Minor gaps remain around pagination beyond 25 and redirect behavior, but the essentials for a correct call are present.

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 100%, so both parameters are already documented, including the default of 20 and max of 25. The description reinforces the cap and clarifies that only unique links are counted against the limit, but adds no new syntax or formatting guidance. Baseline 3 applies when the schema does the heavy lifting.

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 chain (fetch, collect, check) and a precise resource scope: a single page's links. The page-level audit scope is distinguishable from the URL-level siblings in the catalog, though no sibling is named explicitly for routing.

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?

Usage is implied rather than stated: an agent can infer this is for auditing links discovered on an already-known page. There is no explicit when-not guidance, no mention of when to prefer check_url/check_urls on a supplied list, and no prerequisites or exclusions.

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