Skip to main content
Glama

List Network webhook subscriptions

list_network_subscriptions

List webhook subscriptions to Monity Network, including what each follows, its masked destination, and active or stopped status with reason.

Instructions

This key owner's webhook subscriptions to Monity Network: what each follows (a tracker, a person or a site), where it sends (masked), and whether it is active or stopped (with the reason).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: destinations are returned masked, and stopped subscriptions include a reason. It does not state that the operation is read-only, whether results are paginated or ordered, or what happens when the owner has no subscriptions, so gaps remain for a zero-annotation tool.

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?

A single dense sentence with no filler, and the most important content (what each subscription follows and where it sends) comes early. The opening is a noun fragment rather than a verb phrase, which slightly weakens the lead but costs no accuracy.

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 no parameters, no output schema, and no annotations, the description must explain returns, and it does describe the three fields an agent will see. Minor omissions such as pagination and empty-result behavior keep it short of complete.

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 takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly implies no filtering or arguments are needed.

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 names a specific resource and scope: this key owner's webhook subscriptions to Monity Network, and enumerates what each entry covers (followed tracker/person/site, masked destination, active/stopped state). It is clearly distinguishable from the subscribe/unsubscribe/test siblings, though the listing verb itself appears only in the name and title, not the prose.

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 when-to-use statement, no prerequisites, and no mention of alternatives such as subscribe_network_webhook or test_network_webhook. The use case (audit your existing webhooks) is only implied by the described contents.

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