Skip to main content
Glama

Unfollow a tracker

unfollow_tracker

Stops following a Monity tracker by slug or ID when authenticated with a write-scope key, so you can remove trackers from your followed list.

Instructions

Stop following a Monity tracker as this key's owner (needs a write-scope key), by its slug or id.

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

Input Schema

NameRequiredDescriptionDefault
refYesThe tracker's slug or id

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 does disclose the important traits: this is a mutation, it requires a write-scope key, and it is scoped to the key's owner. It stops short of stating idempotency, behavior when not currently following the tracker, or what an error looks like.

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?

One sentence, front-loaded with the action and resource, with the auth caveat inserted tightly in parentheses. No filler or repetition.

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 one-parameter mutation tool with no output schema, the definition covers action, identity, and auth scope — enough to call it correctly. The remaining gap is failure/idempotency behavior, which is minor at this complexity.

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% for the single parameter and the description merely restates it ("by its slug or id"), adding no precedence rule for choosing slug vs. id or any format detail. Baseline 3 is appropriate when the schema already does the documentation 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 pairs a specific verb ("Stop following") with a specific resource ("a Monity tracker"), so the action is unambiguous. The resource noun also implicitly separates it from the similarly named unfollow_network, though it never names that sibling or follow_tracker explicitly.

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 a prerequisite ("needs a write-scope key") and states the acting identity ("as this key's owner"), which implies when the tool is usable. It offers no explicit when-to-use/when-not guidance and no redirection to an alternative such as unfollow_network.

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