Skip to main content
Glama

Publish a monitor to Monity Network

publish_network_watch

Publishes the exact tracker revision shown in preview_network_watch to the person's public Network profile using its revisionId, so the approved version goes live.

Instructions

Step 2 of 2: publish exactly what preview_network_watch showed, with its revisionId. The tracker goes public under the person's Network profile, and they are told in their Monity inbox that this key published it. At most 5 per key per 24 hours; moderation applies as for anyone.

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>",
      "revisionId": "<revisionId>"
    },
    "name": "publish_network_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionIdYesrevisionId from preview_network_watch
monitorUuidYesThe same monitor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.2/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 behavioral burden and does meaningful work: it discloses that the tracker becomes public under the person's Network profile, sends an inbox notification, is capped at 5 per key per 24 hours, and is subject to moderation. It omits whether publishing is reversible or what is returned, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with the sequencing signal ('Step 2 of 2'), then effects, then limits. Every clause carries distinct information with no filler.

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 two-parameter mutation with no annotations and no output schema, the description covers prerequisites, side effects, notification, rate limits, and moderation. The remaining gap is that it never indicates what a successful call returns or how a stale revisionId fails.

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% and both parameters are described in the schema itself, so the baseline is 3. The description reinforces that revisionId must come from the matching preview call and that monitorUuid is 'the same monitor', but adds no format or validation detail beyond the schema.

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 names a specific action and resource (publish a prepared monitor revision) and anchors it to a named sibling: 'publish exactly what preview_network_watch showed, with its revisionId.' An agent can distinguish this from preview and from the other publish/create siblings without opening the schema.

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?

It states the precondition plainly — this is 'Step 2 of 2' and must follow preview_network_watch, reusing that call's revisionId. It does not explicitly contrast with publish_tracker or create_public_tracker, so the agent gets clear context but no stated exclusions.

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