Skip to main content
Glama

Set your condition on a tracker

set_network_condition

Define which changes to a one-source Monity tracker alert its owner about, using structured rules or plain words, and reset to all changes when omitted.

Instructions

Which of a one-source tracker's changes alert this key's owner (needs a write-scope key): a structured condition or plain words (shown back in words). Omit condition to go back to every change.

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

Input Schema

NameRequiredDescriptionDefault
refYesA one-source tracker's slug or id
conditionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations present, the description carries the full disclosure burden, and it does add meaningful context: the write-scope key requirement, the fact that a plain-words condition is rendered back in words, and that omitting the condition resets alerting to every change. It omits the response shape, whether the previous condition is replaced or merged, and any permission failure behavior.

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?

Two tight sentences with no filler, and the authentication constraint plus the reset behavior are stated up front. The opening clause is slightly convoluted ('Which of a one-source tracker's changes alert this key's owner'), which costs a little readability.

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?

For a mutating tool with no annotations and no output schema, the description covers the auth requirement and the two input modes, which is the core need. It does not describe what the call returns or what happens to an existing condition when a new one is supplied, leaving a gap for a write operation.

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?

At 50% schema coverage the description must add some meaning, and it does: it frames the two mutually exclusive modes (structured condition vs plain words) and defines the omitted-condition case, which the schema never states. The nested fields kind/text/words/amount are left to the schema, which documents them adequately.

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 states a specific effect on a specific resource: it decides which of a one-source tracker's changes alert the key's owner. The verb is implied rather than stated outright (it reads as 'sets the alerting condition'), and no sibling such as preview_network_watch is named for differentiation, but the purpose is clear and not tautological.

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 one concrete branch ('Omit condition to go back to every change') and a prerequisite ('needs a write-scope key'), which is real usage guidance. It stops short of saying when to prefer plain words over a structured condition, or when to use this instead of a related tracker tool.

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