Skip to main content
Glama

Stop watching a URL

uptime_remove
DestructiveIdempotent

Stop watching a URL for good: its results and incidents are deleted. An open incident is closed first: the inbox you named gets a "removed" message, your owner a short email if they had the "down" one. Returns deleted: true; an unknown or already removed check_id answers check_not_found. Works after the plan ended.

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": {
      "check_id": "chk_exampleexampleexample2",
      "instance_id": "upt_exampleexampleexample2"
    },
    "name": "uptime_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_idYesThe check's id (chk_...) from uptime_add or uptime_status.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / check_id / description
      Previous value: -"check_id from uptime_add or uptime_status."New value: +"The check's id (chk_...) from uptime_add or uptime_status."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "check_id": "chk_exampleexampleexample2",
      +    "instance_id": "upt_exampleexampleexample2"
      +  }
      +]
    • 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."
  3. 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}$"
  4. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / check_id / description
      Added value: +"check_id from uptime_add or uptime_status."
    • 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."
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes well past the annotations by disclosing concrete destruction ('results and incidents are deleted'), the open-incident resolution sequence (closed first, inbox 'removed' message, owner email only if they had the 'down' notice), the 'deleted: true' response, the check_not_found error, and the notable trait that it works after the plan ended. This is exactly the side-effect detail an agent needs before an irreversible call; it stops short of stating irreversibility in a single explicit word.

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

Conciseness5/5

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

Four tight clauses, front-loaded with the irreversible consequence, then side effects, then return/error contract, then the plan-expiry caveat. No filler or repetition and nothing could be dropped without losing meaning.

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?

With no output schema, the description supplies the return value and error code itself, plus full downstream effects on incidents and notifications. For a destructive three-parameter tool this covers everything required to invoke it correctly and safely.

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 baseline is 3; the description still earns a bump by clarifying check_id behavior on failure ('an unknown or already removed check_id answers check_not_found'). It adds no detail on instance_id or passport_token, which the schema already covers.

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?

States a specific verb and resource ('Stop watching a URL') plus a decisive scope qualifier ('for good: its results and incidents are deleted') that separates it from the add/status siblings. It never names an alternative by name, so the differentiation is implicit rather than explicit.

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 'for good' — this is the permanent removal, not a temporary pause — and the edge case for unknown/already-removed check_ids is spelled out. However, there is no explicit statement of when to prefer this over pausing, disabling, or other removal siblings such as heartbeat_remove.

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.