Skip to main content
Glama

Follow a tracker

follow_tracker

Follow a Monity tracker as its key owner to receive change alerts from every source, with an optional condition to limit alerts to matching updates.

Instructions

Follow a Monity tracker as this key's owner (needs a write-scope key), by its slug or id (as get_tracker and search_network give it): its changes alert them, from every source it has. For a tracker with one source, 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'}). 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_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesThe tracker's slug or id
conditionNoOnly for a tracker with one source

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 does reasonably well: it discloses the auth requirement (write-scope key), the alerting effect ('its changes alert them, from every source it has'), the single-source restriction on conditions, and that app quotas/limits apply. It omits idempotency (what happens if already following) and error behavior, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and the auth requirement, then the identifier form, then the optional condition. Dense but every clause carries information; the parenthetical examples make it slightly run-on but not wasteful.

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 a nested condition object, no annotations, and no output schema, the description covers prerequisites, scope of alerting, condition eligibility, and quota behavior. It leaves the return value and repeat-follow behavior unstated, a modest gap.

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 100%, so baseline is 3; the description adds value by clarifying that ref accepts a slug or id as returned by named siblings and by giving a concrete condition example ({kind: 'BELOW', amount: 150}) plus a plain-words alternative. The single-source constraint is repeated from the schema rather than adding new meaning.

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 ('Follow a Monity tracker as this key's owner') and pins down the identifier form by pointing at the siblings that produce it (get_tracker, search_network). An agent can distinguish this from unfollow_tracker and follow_network 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the prerequisite (write-scope key) and the condition under which the optional parameter is legal ('only for a tracker with one source'). It does not explicitly contrast with follow_network or create_monitor, so the when-not guidance is implied rather than stated.

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