Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Is this URL up right now: live HEAD request from the edge following up to 5 redirects: final URL, status, content type,

url_status
Read-onlyIdempotent

Is this URL up right now: live HEAD request from the edge following up to 5 redirects: final URL, status, content type, server, redirect chain, latency (url=https://example.com). Public hosts only. Pay per call $0.002 USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "url_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNopublic http(s) URL to check
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description goes further by disclosing the 5-redirect follow limit, the exact response fields, the public-hosts restriction, and the x402 payment model including price ($0.002 USDC on Base). It stops short of saying what happens on failure, timeout, or transient network errors.

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?

Content is front-loaded and dense in a single sentence with no filler; the example URL and cost are appended last where they belong. Slight deduction because the title is repeated verbatim and the colon-chained list is harder to parse than separated clauses would be.

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 simple two-parameter read-only probe with full annotations and no output schema, the description covers what is fetched, how many redirects are followed, what is returned, target restrictions, and payment requirements. Only failure/timeout semantics are left unspecified, a minor gap for an uptime check.

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?

Schema coverage is 100%, so both parameters are already documented, including the two-step payment handshake for x_payment. The description adds only the example URL format and the per-call price, which is modest value beyond the schema; baseline 3 is appropriate.

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 and resource: a live HEAD request from the edge against a URL, with the redirect limit and the exact fields returned (final URL, status, content type, server, redirect chain, latency). An agent can immediately tell this apart from siblings like page_meta or security_headers, which imply content/metadata retrieval rather than an up/down probe.

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 implied by the question form 'Is this URL up right now' and constrained by 'Public hosts only', which usefully excludes internal/private targets. However, there is no explicit when-not guidance (e.g. do not use for content extraction or header auditing, where page_meta or security_headers would apply) and no mention of behavior for non-2xx responses or timeouts.

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