Skip to main content
Glama

LinkVet

Check a URL before citing it

check_url
Read-onlyIdempotent

Fetch a URL and verify it is live before you cite or share it. Returns status (live | 404 | blocked | timeout | error | invalid | blocked_ssrf), HTTP code, final URL after redirects, page title, detected price, published/modified dates, and safe_to_cite with a reason. Results are cached ~12h.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe http(s) URL to verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare read-only, idempotent, and open-world; the description adds substantial context beyond that, including the full status taxonomy (including blocked_ssrf), redirect handling via final URL, the safe_to_cite verdict with reason, and a ~12h cache window. These are exactly the behavioral traits an agent needs to interpret results and decide how much to trust a fresh check.

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 sentences, front-loaded with the action and the reason to call it, then a dense enumeration of return fields and the caching caveat. No filler or restatement of the tool name.

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?

With no output schema, the description carries the return-value burden and does so by naming each result field and the possible statuses. For a single-parameter read-only tool, nothing an agent needs in order to call it or interpret the response is missing.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents that a URL is required. The description adds no extra constraints (e.g., http/https-only, whether fragments or query strings matter) beyond what the schema states, so the baseline of 3 applies.

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 (fetch a URL and verify it is live) plus the intent (before citing or sharing), which an agent can act on directly. It does not differentiate itself from the sibling check_urls, so an agent cannot tell from this text alone which of the two to pick.

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 use condition: run it before you cite or share a link. There is no explicit when-not guidance and no named alternative such as check_urls, so the routing decision between the single and batch variants is left to inference.

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