Skip to main content
Glama

Watch a URL

uptime_add

Watch an https URL of your live app with your uptime-watch (up to 3 URLs). We check it every 5 minutes; 2 failures in a row (or 3 of the last 5) open an incident: a message in the inbox you name and one email to your owner (once they confirmed their address). Recovery sends one "back up" message and email. Returns the check (id chk_...); the same URL again answers check_exists. A job that pings us instead: heartbeat_add.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://example.com/health",
      "instance_id": "upt_exampleexampleexample2"
    },
    "name": "uptime_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https URL, at most 2048 characters, e.g. https://your-app.example.com/health
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.
inbox_instance_idNoOne of your webhook inboxes, to be woken there when the URL goes down or comes back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "upt_exampleexampleexample2",
      +    "url": "https://example.com/health"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false; the description goes well beyond that with the 5-minute check cadence, the two failure thresholds, the exact notification fan-out (one inbox message plus one owner email, contingent on confirmed address), and the single recovery message. That is real operational context. It leaves out quota/rate behavior around the 3-URL cap and whether an incident blocks further checks, which keeps it off a 5. No contradiction: returning check_exists on a repeat is consistent with idempotentHint=false, since the response differs.

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?

Front-loaded with the action and the cap, then escalates to monitoring semantics, return value, and the sibling alternative in a tight semicolon-separated sequence. Every clause carries information, though the run-on sentence structure makes the thresholds and the return-value contract slightly harder to scan than they need to be.

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

Completeness5/5

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

For a four-parameter mutation tool with no output schema, the description closes the gaps that matter: what gets created ("Returns the check (id chk_...)"), what happens on duplicate input, what side effects fire on failure and recovery, and which sibling covers the inverse case. Nothing an agent needs in order to call this correctly is missing.

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 the baseline is 3 and the schema already documents all four parameters including the 2048-char https constraint. The description adds only marginal semantics beyond that — the inbox is where the down/up message lands, and the 3-URL account ceiling — while passport_token gets no mention in either field beyond its own schema text.

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 ("Watch an https URL of your live app") plus a hard scope limit ("up to 3 URLs"), and explicitly distinguishes the inverse pattern in the same breath: "A job that pings us instead: heartbeat_add." An agent can separate this from heartbeat_add without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the when (https URL of a live app you want probed from outside), the when-not (use heartbeat_add when the job pings you rather than you pinging it), and the duplicate case ("the same URL again answers check_exists"). All three routing decisions are stated rather than inferred.

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.