Skip to main content
Glama

Find an existing public tracker before creating a monitor

find_existing_network_watch

Find public Monity Network trackers that already check a page the same way before creating a monitor. Follow an existing one to get the same alerts, or see how same-page trackers differ.

Instructions

Call this before create_monitor. Returns public Monity Network trackers that already check this page the same way (same: follow one instead of creating a monitor; the person gets the same alerts and nobody pays for a second check), and trackers of the same page that check it differently (samePage, with what differs: region, keywords, conditions…). shareable is false for pages that need cookies, headers or actions.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe page address
keywordsNoComma-separated keywords, if the monitor will look for words
notifyWhenNoThe alert condition, if any
compareTypeNo
keywordsActionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.1/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 disclosure load and does well: it describes the two result buckets and their field names ("same", "samePage", with differing region, keywords, conditions), and flags that shareable is false for pages needing cookies, headers or actions, which tells the agent some pages cannot become shared trackers at all. It stops short of stating that the tool itself is read-only, and says nothing about auth or the result set when nothing matches.

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 call-to-action ordering comes first, then the two result categories, then the shareable caveat — good front-loading. The parenthetical explaining why following saves money and avoids duplicate billing is motivational padding rather than call-relevant detail.

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 five-parameter, no-annotation, no-output-schema lookup tool, the description gives enough: when to call it, what the two result shapes mean, and the shareable constraint. The remaining gap is parameter behavior — compareType and keywordsAction are left for the agent to infer.

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 60%, mid-range, and the description only implicitly maps inputs to the search: keywords and conditions are named as things that may differ, hinting at why keywords/notifyWhen exist. It says nothing about compareType (the enum) or keywordsAction, which have little or no schema documentation, so the two weakest parameters stay unexplained.

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?

It states a specific verb and resource — find/return public Monity Network trackers for this page — and immediately distinguishes two result classes ("same" vs "samePage"). The distinction from create_monitor is explicit, so an agent can tell what this tool is not.

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?

"Call this before create_monitor" gives an explicit ordering rule, and "follow one instead of creating a monitor" names the alternative action with its payoff. The missing piece is a when-not case: nothing says what to do if a match shares nothing meaningful in common, or whether to call this for private or non-shareable pages.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.