Skip to main content
Glama

Topolograph

get_adjacency_events

Read-onlyIdempotent

Description: This tool returns links/adjacencies events including nodes/hosts up/down events. Use this tool only to get details about nodes/hosts 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: AdjacencyEventsResponse: A dictionary containing adjacency event information with keys: - all_host_up_down_events: List of all Up/Down nodes/hosts events (Восстановление узла, Падение узла). List includes all events even recovered events (when node is up after being down). - single_host_up_events: List of Up nodes/hosts events (Восстановление узла) from the time when graph was collected. - single_host_down_events: List of Down nodes/hosts events (Падение узла) from the time when graph was collected. - adjacency_cost_change_events: List of link/adjacency cost (or other metrics) change events (изменение стоимости линка)

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

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

Input Schema

NameRequiredDescriptionDefault
end_timeNo
graph_timeYes
start_timeNo
last_minutesNo

Output Schema

NameRequiredDescriptionDefault
single_host_up_eventsYes
all_host_up_down_eventsYes
single_host_down_eventsYes
adjacency_cost_change_eventsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, destructive=false, openWorld, so the safety profile is covered; the description adds genuinely beyond that: a data-availability rule tied to monitoring state, a prerequisite call chain, the -1 cost-change convention for interpreting up/down, and the last_minutes override behavior. It does not mention pagination, result size, or how far back events are retained, which keeps it from a 5.

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 critical routing and prerequisite information is front-loaded in the first three sentences, before any parameter detail. The Input/Output sections are labeled and scannable, though the 'Description:' prefix, the bilingual Russian glosses, and an output-field listing that partly duplicates the existing output schema add bulk that could be trimmed.

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 a rich annotation set and an existing output schema, the description covers everything an agent needs to invoke correctly: prerequisite discovery call, monitored-graph constraint, time-window parameter semantics including precedence, and interpretation rules for the returned event lists. Nothing material is missing for a read-only filtered event query.

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 description coverage is 0%, so the description must carry the burden and largely does: all four parameters get meaning, start_time/end_time get ISO format (2025-06-30T20:00:00Z) and end_time's default, and last_minutes is documented as overriding start/end. The one weak spot is graph_time, described circularly as 'Name of graph = The graph time to filter events', which is precisely the field an agent must obtain from get_all_graphs.

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?

States a specific verb+resource: returns link/adjacency events and node/host up-down events, and adds a narrowing sentence ('Use this tool only to get details about nodes/hosts events' although it also returns adjacency cost changes). An agent can distinguish it from generic graph/nodes tools, but overlapping siblings such as get_events_timeline or get_network_events are never named, so differentiation is only partial.

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

Usage Guidelines4/5

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

Unusually strong for this set: it gives a precondition (events exist ONLY for watcher-monitored graphs, is_monitored=true), an explicit when-not (manually uploaded or YAML graphs have no events), and a concrete prerequisite sequencing instruction to call get_all_graphs(is_monitored=true, latest_only=true) first. It stops short of routing the agent to a sibling for other event types, so it is clear context rather than full alternative coverage.

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.