Skip to main content
Glama

verify_links

Read-only

Check up to 10 URLs before citing or sending them. Per URL: verdict (live, live_but_text_not_found, soft_404, parked, dead, blocked_or_rate_limited, unreachable), HTTP status, final URL, title, and optional check that an expected phrase appears. Price: 0.005 USDC per call (x402, Base).

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

Input Schema

NameRequiredDescriptionDefault
urlsYesURL strings, or {url, expect} objects

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description did not need to re-establish that this is a safe network read. It contributes genuine extra context: per-call price and payment rail (0.005 USDC via x402 on Base), and the fact that results can be 'blocked_or_rate_limited' or 'soft_404', warning the agent about ambiguous outcomes. It omits timeout/retry behavior and any wallet-setup prerequisite for paying.

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?

Two dense sentences with the purpose and scope front-loaded, followed by the return fields and then cost. Nothing is padded or repeated; the verdict list is compressed into a single parenthetical.

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

Completeness5/5

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

There is no output schema, so the description must carry the return-value burden and does, defining the verdict taxonomy plus status/final URL/title. Combined with the pricing note and the schema's URL/expect structure, an agent has everything needed to call it correctly.

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 description coverage is 100%, so baseline is 3, and the description adds real meaning on top: it explains that the optional field is an expected-phrase check ('optional check that an expected phrase appears'), which the schema only hints at via the 'expect' property name. The 'up to 10 URLs' cap is restated from maxItems rather than newly explained.

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 (check) and resource (URLs) with explicit scope ('up to 10') and enumerates the verdict vocabulary returned. An agent can tell this is a live web-link checker with phrase-verification, not an archive lookup or citation formatter.

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 a clear usage context: 'before citing or sending them', which tells the agent when to reach for this tool. It does not name alternatives or state exclusions (e.g., when to prefer verify_citations or find_archive), so it stops short of full routing guidance.

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