Skip to main content
Glama

Follow a tracker or a person

follow_network

Follow trackers or people on Monity Network to receive change alerts; optionally set personal conditions for one-source trackers without affecting other followers.

Instructions

Follow on Monity Network as this key's owner (needs a write-scope key): a tracker (its changes alert them; targetType WATCHLIST for a tracker with several sources, WATCH for a tracker with one source) or a person (HUNTER: their new trackers). follow_tracker works out the kind of tracker itself. For a one-source tracker, optionally a personal condition so only matching changes alert them (e.g. {kind: 'BELOW', amount: 150}, or {words: 'only when it is back in stock'}). Other followers are unaffected. Same quotas and limits as the app.

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

Input Schema

NameRequiredDescriptionDefault
refYesA tracker's slug or id, or a person's handle
conditionNo
targetTypeNoDefault WATCH (a tracker with one source); WATCHLIST for a tracker with several, HUNTER for a person

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it discloses several non-obvious behaviors: the write-scope key requirement, that the follow is attributed to the key's owner, that other followers are unaffected, and that app quotas/limits apply. It stops short of stating idempotency (what happens when already following) or what a successful response contains.

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 prerequisite and the core action are front-loaded, and nearly every clause carries information. The nested parentheticals and the mid-sentence aside about follow_tracker make it denser to parse than it needs to be, but there is 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 an unannotated mutation tool with a nested condition object and no output schema, the description covers authorization, quota, blast radius, target-type selection, and condition applicability. The remaining gaps (return value, duplicate-follow behavior) are modest for a tool of this complexity.

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 67%, and the description meaningfully closes much of the gap: it maps WATCHLIST to a multi-source tracker, WATCH to a single-source tracker, and HUNTER to a person, and it explains that condition applies only to one-source trackers with concrete examples ({kind: 'BELOW', amount: 150}, {words: '...'}). It does not further clarify the `ref` parameter, but the schema already describes slug/id/handle.

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?

The description opens with a specific verb and resource ("Follow on Monity Network") and enumerates the two things that can be followed: a tracker or a person, with the corresponding targetType values. It distinguishes itself from follow_tracker only obliquely ("follow_tracker works out the kind of tracker itself"), leaving a slight ambiguity about which tool to reach for, but the core purpose is unmistakable.

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?

It gives an important prerequisite ("needs a write-scope key") and names follow_tracker as a related option, but the selection rule between them is only hinted at. Usage for a person (HUNTER) and for a one-source tracker with a condition is implied through the targetType/condition explanation rather than stated as an explicit when-to-use rule.

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