Skip to main content
Glama

Url status

url_status
Read-onlyIdempotent

Check URL HTTP reachability, full redirect chain, latency, content type, and HTTPS end status. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, openWorld and non-destructive, so the safety profile needs no restatement. The description adds information the annotations cannot convey: a per-call price ($0.001), the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the two-step handshake required before a paid call succeeds. It omits failure semantics such as timeouts or what a signed-payment rejection looks like.

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?

Three sentences, front-loaded with the capability list before cost and payment mechanics, and every sentence carries distinct information. Slightly dense in the payment-rails clause, but no filler or repetition.

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 read-only, single-URL diagnostic with no output schema, the description supplies the return dimensions the agent would otherwise have to discover empirically, plus the payment protocol needed to actually complete a call. The remaining gap is error/timeout behavior, which is minor for this tool class but would matter for an agent polling unreliable hosts.

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?

With 100% schema description coverage, the schema already defines both 'url' and 'payment', so the baseline is 3. The description does add the sequence semantics the schema does not state — that the first call is made without 'payment' to obtain terms — but it adds nothing about URL formatting or edge cases beyond the schema's 'public http(s) URL'.

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?

The description opens with a precise verb ('Check') and resource ('URL') and enumerates exactly what is reported: HTTP reachability, full redirect chain, latency, content type, and HTTPS end status. That is enough to separate it from extraction-oriented siblings like page_extract or html_to_markdown, though it never explicitly names an alternative such as link_check, which is its closest overlap.

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 guidance exists but is procedural rather than selective: 'Call once without payment for the terms, sign them with your own wallet, call again with payment' tells the agent how to sequence calls, which is genuinely useful. It gives no guidance on when to prefer this over link_check or other status-adjacent siblings, and no exclusions or prerequisites beyond the payment loop.

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