Skip to main content
Glama

LinkVet

Check up to 25 URLs at once

check_urls
Read-onlyIdempotent

Batch version of check_url: verify up to 25 URLs in one call (e.g. every link in an answer you are about to send). Returns one result per URL in input order.

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

Input Schema

NameRequiredDescriptionDefault
urlsYesList of http(s) URLs (max 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety and side-effect profile is covered. The description adds two genuinely non-structured behavioral facts: the 25-URL ceiling and the guarantee that results come back one-per-URL in input order. It does not say what happens on partial failure or what "verify" concretely measures, which keeps it from a 5.

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 with zero filler: the batch identity and limit are front-loaded, followed by a use case and the return-ordering guarantee. Nothing is repeated unnecessarily and nothing could be cut without losing information.

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?

For a single-parameter, read-only tool with full schema coverage and annotations, the description supplies what structured fields cannot: batch semantics, the return ordering, and a motivating scenario. The one remaining gap is that "verify" is never unpacked (reachability vs. status codes vs. redirect handling), which matters more given there is no output schema to clarify the return values.

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?

Only one parameter exists and the schema already documents it at 100% coverage, including the max-25 constraint. The description's "e.g. every link in an answer you are about to send" adds useful intent-level meaning about what should go in the list, but it largely restates the schema's array-of-URLs definition, so the baseline of 3 applies.

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?

"Batch version of check_url: verify up to 25 URLs in one call" names a specific verb (verify), resource (URLs), and batch scope, and explicitly anchors itself to the sibling check_url. An agent can distinguish it from the single-URL sibling without inspecting either schema.

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?

The description gives a concrete selection context — "every link in an answer you are about to send" — and labels itself the batch counterpart of check_url, which implies the single-URL tool for individual checks. It stops short of an explicit "use check_url instead when you have one URL" exclusion, so it falls just below the top score.

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