Skip to main content
Glama

Topolograph

get_bgp_events_timeline

Read-onlyIdempotent

BGP monitoring events (session up/down, route churn), grouped into a timeline by default.

Input fields: bgp_graph_time (str): The BGP graph epoch to query start_time (str, optional), end_time (str, optional): ISO 8601 window last_minutes (int, optional): Look back this many minutes from end_time (default now); overrides start_time event_name (str, optional), event_status (str, optional): Filters as_rows (bool, optional): Return one flat row per event instead of the timeline aggregate

Equivalent to GET /bgp-graph/{bgp_graph_time}/events.

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": {
      "bgp_graph_time": "<bgp_graph_time>"
    },
    "name": "get_bgp_events_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_rowsNo
end_timeNo
event_nameNo
start_timeNo
event_statusNo
last_minutesNo
bgp_graph_timeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds real behavioral detail beyond them: results are aggregated by default, as_rows switches to flat rows, and last_minutes takes precedence over start_time (defaulting the anchor to now). It does not mention pagination or result limits on a potentially large event stream.

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?

Front-loaded with the core purpose, then a compact field list that mirrors the schema ordering. The type restatements are somewhat redundant but justified given 0% schema description coverage; nothing is padded or off-topic.

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?

Annotations and an output schema reduce what the description must carry, and it documents every parameter. However, it leaves ambiguity on the bgp_graph_time format (called a 'str' but described as an 'epoch') and on valid event_name/event_status values, which for a 7-parameter query tool is a meaningful residual gap.

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 0% schema coverage across 7 parameters, the description carries the full burden and mostly succeeds: it assigns types and meaning to bgp_graph_time, the ISO 8601 window, the last_minutes lookback and its override precedence, and the as_rows toggle. The gaps are event_name/event_status, whose accepted filter values and matching semantics are never described.

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?

Names a specific resource (BGP monitoring events: session up/down, route churn) tied to a specific graph epoch, plus the default aggregation mode. It does not explicitly distinguish itself from near-siblings such as get_events_timeline or get_route_events, so an agent must infer the boundary from the 'BGP' qualifier alone.

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 only implied: the description states the default is a grouped timeline and that as_rows flattens it, which tells the agent how to pick an output shape. It gives no guidance on when to choose this tool over get_events_timeline or the other event/route tools, and no 'when not to use' exclusions.

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.