Skip to main content
Glama

Check URL

check_url

Request a public URL and report status, final URL, latency, content type, size, TLS, and a few response headers. Does not follow into private networks.

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
urlYesPublic http or https URL. No private addresses, no credentials.

Output Schema

NameRequiredDescriptionDefault
okNo
sizeNo
errorNo
statusNo
tls_okNo
headersNo
messageNo
final_urlNo
latency_msNo
content_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose two valuable traits: the request targets public URLs only and the tool will not follow into private networks, and it enumerates returned fields so the agent knows what comes back. It stays silent on timeouts, error/status-code handling, redirect policy (only implied by 'final URL'), request method, and any rate limits, which are real gaps for an unannotated network tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the capability statement front-loaded before the scope constraint. Slightly more could be gained by folding the constraint into a when-to-use clause, but nothing is wasted.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and for a single-parameter tool the coverage is close to sufficient. Missing are operational details that matter for a network probe with no annotations – timeouts, what happens on non-2xx responses, and whether the body is ever returned – leaving the agent to discover them at call time.

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?

One parameter at 100% schema coverage, so the schema already defines it as a public http/https URL with no private addresses and no credentials. The description's constraint about private networks merely restates that, adding no new meaning about format, normalization, or how to handle edge cases like ports or query strings.

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?

Names a specific verb (request) plus the resource (public URL) and enumerates exactly what it reports: status, final URL, latency, content type, size, TLS, and headers. That reads as a diagnostic probe rather than a content fetcher, which is what separates it in spirit from read_url and fetch_page, but the description never names or explicitly contrasts those siblings.

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 only implied by the output fields (status, latency, TLS) – an agent can infer this is for reachability and health checks rather than reading page content. The single negative constraint about private networks limits scope but is a capability boundary, not a when-to-use/when-not rule, and no alternative tool is named.

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