Skip to main content
Glama

Preview publishing a monitor to Monity Network

preview_network_watch

Preview what would become public before publishing a monitor as a Monity Network tracker, including eligibility, shared fields, similar public trackers, and a revision ID for approval.

Instructions

Step 1 of 2 to publish one of this account's monitors as a public Monity Network tracker (needs an API key with the network:publish scope). Returns exactly what would become public (preview: title, slug, scope, site, cadence, shares[] and doesNotShare[]), whether it is eligible (reasons if not), public trackers of the same page (samePage: suggest following one, or give a scope saying how yours differs), and a revisionId. Nothing is public after this. Show the person the preview and get their go-ahead before publish_network_watch. Create the monitor first with create_monitor if needed; a monitor becomes eligible once it has checked successfully.

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": {
      "monitorUuid": "<monitorUuid>"
    },
    "name": "preview_network_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoWhat exactly it covers, e.g. "UK store, size 10"
titleNoPublic title (default: the monitor name)
categoryNoA Network topic, e.g. deals, tech, jobs
descriptionNoWhy it is worth following
monitorUuidYesThe monitor to publish (from list_monitors or create_monitor)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: it discloses the required auth scope (network:publish), states the safety-critical property that "Nothing is public after this," and explains what the read returns including eligibility verdicts with reasons. Reversibility, side effects, and prerequisites are all covered.

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 purpose and sequencing, and every clause carries information — auth scope, return shape, eligibility, next step. The single dense paragraph is slightly overloaded with parenthetical enumerations, which costs a point on scannability but not on substance.

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 annotations and no output schema, the description compensates fully: it enumerates the return payload, flags the eligibility outcome, names the continuation tool, and covers the prerequisite chain. Nothing an agent needs to call this correctly or interpret its result 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 description coverage is 100%, so the schema already documents all five parameters including the scope example and title default. The description adds only marginal parameter meaning (scope as the differentiator when a samePage tracker exists, monitorUuid provenance hint via create_monitor), which is the baseline expected when the schema does the heavy lifting.

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 ("preview publishing a monitor as a public Monity Network tracker") and positions itself explicitly as "Step 1 of 2" relative to publish_network_watch. The returned payload is enumerated (title, slug, scope, site, cadence, shares[], doesNotShare[], samePage, revisionId), so an agent knows exactly what this tool produces versus its siblings.

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 explicit sequencing ("Show the person the preview and get their go-ahead before publish_network_watch"), a prerequisite ("Create the monitor first with create_monitor if needed"), and the eligibility precondition ("a monitor becomes eligible once it has checked successfully"). It also names a routing decision inside the response: follow an existing samePage tracker or justify a differing scope.

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