Skip to main content
Glama
io.github.ryanmat/logicmonitor

io.github.ryanmat/logicmonitor

by ryanmat

analyze_blast_radius

Read-onlyIdempotent

Analyze a device failure's blast radius by counting neighboring and dependent devices through topology paths, reporting alert status and critical path devices while flagging unreadable reads.

Instructions

Count the devices a device failure could reach through topology neighbors: neighbor_count at depth 1, dependent_count beyond it, each device's alert status, and critical path devices. A device whose neighbors neither topology path answers is listed under unreadable with a warning, never counted as zero; on a portal without those routes every read is unreadable.

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": {
      "device_id": "<device_id>"
    },
    "name": "analyze_blast_radius"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoMax traversal depth (1-3)
device_idYesDevice ID to analyze

Output Schema

NameRequiredDescriptionDefault
depthYes
portalNoThe portal the call ran against, in multi-portal mode.
warningNo
degradedNo
device_idYes
unreadableYes
neighbor_countYes
degraded_detailNo
dependent_countYes
affected_devicesYes
critical_alert_countYes
critical_path_devicesYes
total_affected_devicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "affected_devices": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "critical_alert_count": {
      +      "type": "integer"
      +    },
      +    "critical_path_devices": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "degraded": {
      +      "type": "boolean"
      +    },
      +    "degraded_detail": {
      +      "type": "string"
      +    },
      +    "dependent_count": {
      +      "type": "integer"
      +    },
      +    "depth": {
      +      "type": "integer"
      +    },
      +    "device_id": {
      +      "type": "integer"
      +    },
      +    "neighbor_count": {
      +      "type": "integer"
      +    },
      +    "portal": {
      +      "description": "The portal the call ran against, in multi-portal mode.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "total_affected_devices": {
      +      "type": "integer"
      +    },
      +    "unreadable": {
      +      "type": "array"
      +    },
      +    "warning": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "device_id",
      +    "depth",
      +    "total_affected_devices",
      +    "neighbor_count",
      +    "dependent_count",
      +    "affected_devices",
      +    "critical_path_devices",
      +    "critical_alert_count",
      +    "unreadable"
      +  ],
      +  "type": "object"
      +}
  2. First observedv4.2.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish this as a safe, read-only, idempotent operation. The description adds meaningful behavioral context beyond annotations: unreadable results are warned about and never treated as zero, and portals without topology routes make every read unreadable.

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 description is only two sentences and front-loads the core purpose. The second sentence is dense and slightly awkward, but it carries important unreadable-result semantics rather than filler.

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

Completeness5/5

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

For a two-parameter read-only topology analysis tool with a full input schema, rich annotations, and an output schema, the description covers purpose, output categories, and exceptional result handling. Nothing essential for correct invocation appears missing.

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?

Schema coverage is complete, so the baseline is 3, but the description adds useful meaning to depth by explaining that depth 1 produces neighbor_count and deeper traversal produces dependent_count. Device ID semantics are obvious and left to the schema.

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 verb and resource: counting devices reachable through topology neighbors after a device failure. It clearly defines the blast-radius analysis and output categories, though it does not explicitly distinguish itself from sibling analysis tools.

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?

Usage is implied by the failure-impact framing and topology traversal, but the description gives no explicit when-to-use or when-not-to-use guidance versus alternatives such as diagnose or detect_site_outage. An agent can infer the context but receives no routing rules.

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

Deploy Server

Other Tools