Skip to main content
Glama

List what you follow on Network

list_network_follows

List the trackers and people a key owner follows on Monity Network, directly or via followed trackers, including each follow's alert settings.

Instructions

The trackers and people this key's owner follows on Monity Network (directly, or as a source of a tracker they follow), with their alert settings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_network_follows"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that results include both direct follows and follows arising as tracker sources, along with alert settings, but it does not explicitly state read-only behavior, authorization scope, pagination, or return ordering.

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 definition is a single compact sentence with no wasted wording, and the scope detail is included efficiently. However, it is structured as a noun phrase rather than front-loading the listing action, so it is slightly less direct than it could be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and parameterless, and the description covers what is returned plus the direct/indirect follow scope. It still leaves gaps around sibling selection and does not clarify read-only behavior or result shape, which matters because no output schema or annotations are provided.

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?

The tool has zero parameters, so there is no parameter semantics to clarify beyond the schema. The baseline for a parameterless tool is 4, and the description does not need to compensate for undocumented inputs.

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 as the trackers and people the key's owner follows on Monity Network, and clarifies scope by including indirect follows used as tracker sources. It is clear what data is being listed, but the wording is a noun phrase rather than a direct listing verb and does not explicitly distinguish itself from sibling tools such as list_network_subscriptions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool instead of alternatives like list_network_subscriptions, follow_network, or list_monitors. The name implies it is a listing read, but the description provides no when-to-use conditions, exclusions, or alternative routing.

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