Skip to main content
Glama

Link check

link_check
Read-onlyIdempotent

Check up to 12 comma-separated URLs in parallel for broken links, HTTP statuses and redirect chains. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
urlsYescomma-separated http(s) URLs, up to 12
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say read-only, open-world, idempotent and non-destructive. The description adds the facts an agent actually needs: parallel execution, a 12-URL batch cap, a concrete price ($0.003/call), accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the x402 handshake required before work happens. This is exactly the context structured fields don't carry.

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?

Three sentences, front-loaded with capability and constraints, then cost, then the invocation protocol. No filler, and the most easily-missed detail (the two-call payment flow) is stated last but plainly.

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?

There is no output schema, yet the description implies what comes back (per-URL broken status, HTTP status, redirect chain) without specifying structure or per-URL error reporting within a batch. For a small 2-parameter tool with annotations covering safety, this is close to complete; only the return shape is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns a step up by explaining the lifecycle of `payment` — omit it first to receive terms, then pass the signed payload so the purchase completes inside the call. The schema only labels it 'a signed x402 payment', so this sequencing meaning is genuinely new.

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?

States a specific verb and resource ('Check ... URLs') plus the checked attributes (broken links, HTTP statuses, redirect chains) and a hard scope limit of 12. It is clear what the tool does, but it never distinguishes itself from the closest sibling, url_status, so the agent must infer the difference.

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

Usage Guidelines4/5

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

Gives an explicit two-step invocation sequence: call once without `payment` to get terms, sign with your own wallet, call again with `payment`. That is concrete operational guidance with a clear condition for each call. What's missing is guidance on when to prefer this over url_status or page_links.

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