Skip to main content
Glama

Uptime monitor

uptime_monitor

Watch one public HTTP/HTTPS URL every ~10 minutes for 24 hours ($0.01). Pass url= to start/extend or id= to read checks. $0.01 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

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

Input Schema

NameRequiredDescriptionDefault
idNo32-hex watch id to read status
urlNopublic http(s) URL to monitor
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

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses important behavior: monitoring frequency, 24-hour duration, cost, payment asset options, and the two-step x402 payment sequence requiring a wallet signature. It omits details about what happens after 24 hours and the exact return format.

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?

The definition is front-loaded with purpose and usage, then payment mechanics. It is dense but mostly earns its length; the price is stated twice, which is slightly repetitive but not harmful.

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?

For a tool with no annotations and no output schema, the description covers invocation and payment well but leaves gaps around what reads return, what happens at the end of the 24-hour window, and how extension semantics work. It is adequate but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful context beyond the schema: url starts or extends monitoring, id reads checks, and payment requires a first call without payment followed by a signed second call. This clarifies the otherwise opaque x402 payment parameter.

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?

The description states a specific verb and resource: watch one public HTTP/HTTPS URL, with the interval and duration defined. An agent can immediately tell this tool is for uptime monitoring rather than any sibling operation.

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?

It clearly distinguishes the two usage modes: pass url= to start or extend a watch, or id= to read checks. It also explains the required payment flow. It does not state when not to use the tool, but the operational context is strong.

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