Skip to main content
Glama

Get a Monity tracker

get_tracker

Fetch a public tracker by slug or ID to inspect its one or multiple source pages, health, followers, and publisher on the Monity Network.

Instructions

One public tracker, whatever its sources: what people follow on Monity Network. sources is ONE (the page it tracks, its health, followers, who runs it) or SEVERAL (each source a page Monity checks, credited to whoever publishes it, or an external source such as an agent, labelled; each source's health; its followers). Use get_network_changes with watch= (ONE) or watchlist= (SEVERAL) for what changed.

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_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesTracker slug or id (from search_network or list_starter_packs)

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?

No annotations exist, so the description carries the full behavioral burden, and it does substantial work: it discloses the returned structure (per-source health, followers, publisher credit, external/agent sources being labelled) and scopes the tool to public trackers only, implying access limits. It does not state error behavior for unknown or non-public refs, which is the main remaining gap for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The purpose is front-loaded, but the middle sentence is a long string of parentheticals that is hard to parse on a first read and mixes return-shape detail with cross-tool routing. The content earns its place, yet the packaging could be tightened considerably without losing information.

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?

With one required parameter, no output schema, and no annotations, the description must explain both selection and return content, and it does explain the two source shapes and their per-source fields. Only the absence of failure-mode behavior (invalid ref, private tracker, not found) keeps it from being fully complete.

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 the schema already documents `ref` as a tracker slug or id sourced from search_network or list_starter_packs. The description only indirectly reinforces this by using `<ref>` as the same identifier in the get_network_changes alternative. Baseline 3 is appropriate since the schema does the work.

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 identifies the resource precisely (a single public tracker on Monity Network) and, unusually, defines what a tracker is by describing the two shapes its `sources` can take. It reads as a noun phrase rather than a verb+resource statement, so the retrieval action comes mostly from the title, but an agent can still tell this apart from listing or change-query tools.

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 names an explicit alternative and the condition that selects it: use get_network_changes with watch=<ref> for the ONE case or watchlist=<ref> for the SEVERAL case when you want what changed rather than the current state. That is real routing guidance. It stops short of exclusions against the many other get_* siblings (get_network_watch, get_network_product, get_monitor), so the agent must infer those boundaries.

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