Skip to main content
Glama

Topolograph

get_network_events

Read-onlyIdempotent

Description: This tool returns networks events: network up/down and network cost change events. Use this tool only to get details about networks events. Events exist ONLY for watcher-monitored graphs (is_monitored=true). Manually uploaded or YAML graphs are not monitored and have no events; first call get_all_graphs(is_monitored=true, latest_only=true) to pick a monitored graph_time. Treat any cost change to or from -1 as down (падение) or up (восстановление) event.

Input fields: graph_time (str): Name of graph = The graph time to filter events. start_time (str, optional): Start time to filter events in ISO format (e.g., 2025-06-30T20:00:00Z) end_time (str, optional): End time to filter events in ISO format. Defaults to current time if not provided. last_minutes (int, optional): Number of minutes to look back from current time for events. If provided, overrides start_time and end_time parameters.

Output fields: NetworkEventsResponse: A dictionary containing network event information with keys: - network_up_down_events: List of NetworkUpDownEvent objects - network_cost_change_events: List of NetworkMetricChangeEvent objects

Equivalent to GET /events/{graph_time}/networks.

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": {
      "graph_time": "<graph_time>"
    },
    "name": "get_network_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_timeNo
graph_timeYes
start_timeNo
last_minutesNo

Output Schema

NameRequiredDescriptionDefault
network_up_down_eventsYes
network_cost_change_eventsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the data-availability constraint (only monitored graphs produce events), a semantic rule for interpreting cost changes to or from -1 as up/down events, and the default that end_time falls back to now. It also anchors the tool to an underlying API endpoint, giving the agent confidence about what is actually read.

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?

Purpose and the monitoring prerequisite are front-loaded, and the Input/Output field layout is easy to scan. There is mild redundancy ("returns networks events" restated as "only to get details about networks events"), a stray "Description:" label, and a non-English gloss (падение/восстановление), but nothing that obscures the call.

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?

Given four parameters, zero schema coverage, and a prerequisite chain involving another tool, the description supplies everything needed to call it correctly: graph selection, time-window options with precedence, expected event categories, and the empty-result case for unmonitored graphs. Return shape is already captured by the output schema, so restating the response keys is harmless surplus.

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?

With schema description coverage at 0%, the description carries the full burden and mostly does: it gives ISO format and an example for start_time/end_time, the current-time default for end_time, and the override precedence for last_minutes. The graph_time explanation is garbled ("Name of graph = The graph time to filter events"), leaving the required parameter the least clearly defined of the four.

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 uses a specific verb+resource ("returns networks events: network up/down and network cost change events") and scopes it to a single graph_time, which separates it from event siblings such as get_adjacency_events or get_route_events. It stops short of explicitly naming any alternative tool, so the differentiation is inferred from the event category rather than stated.

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

Usage Guidelines5/5

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

It states an explicit use restriction ("Use this tool only to get details about networks events") and a hard prerequisite: events exist ONLY for watcher-monitored graphs, with a concrete first step of calling get_all_graphs(is_monitored=true, latest_only=true) and the exclusion that manual/YAML uploads have no events. It also documents parameter interplay (last_minutes overrides start_time and end_time).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.