Skip to main content
Glama

Get a Network tracker

get_network_watch

Retrieve details for a single-source public tracker, including tracked page, scope, health, followers, owner, and latest before/after changes.

Instructions

One public tracker with a single source: what page it tracks (host and address), its scope, whether it is still live (health), followers, who runs it, and its latest changes with before/after values. For a tracker with several sources use get_tracker. Use get_network_changes for more history, get_network_update for one change's evidence.

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": {
      "ref": "<ref>"
    },
    "name": "get_network_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesIts slug or id (a tracker with one source, from search_network)
recentNoHow many latest changes to include (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.3/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 it does disclose the shape of the read payload (health status, followers, owner, changes with before/after values) plus the fact that the tracker is public and single-source. It stops short of stating failure behavior for an unknown or non-public ref, or any rate/auth constraints, which for a read tool with no annotations leaves a small gap.

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, each doing distinct work: first the payload, then the sibling routing. It is front-loaded and free of filler, though the opening sentence is a dense parenthetical-laden field list that reads more like an inventory than a lead.

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?

There is no output schema and no annotations, so the description has to describe return values itself, which it largely does by enumerating the returned fields including before/after change values. What it omits is edge behavior (unresolvable ref, non-public tracker) and whether 'scope' or 'health' have restricted value sets, which an agent would need to interpret results.

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: 'ref' as slug-or-id from search_network and 'recent' with its default of 5 are already fully documented in the schema. The description reinforces the ref semantics ('a tracker with one source') and that returned 'latest changes' are what recent controls, but adds no new format or constraint detail.

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 ('One public tracker with a single source') and enumerates exactly what comes back: tracked page host/address, scope, health, followers, owner, and latest changes with before/after values. It explicitly distinguishes itself from get_tracker by scoping to single-source trackers, so an agent can pick it apart from the multi-source sibling without opening a 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?

It names three concrete alternatives with the exact condition that selects each: get_tracker for a multi-source tracker, get_network_changes for more history, get_network_update for one change's evidence. That is an explicit when-to-use-this/when-to-use-something-else routing rule, not implied guidance.

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