Skip to main content
Glama

Topolograph

get_graph_status

Read-onlyIdempotent

Get the status of a graph based on its health.

Description: This tool returns the status of a graph including connectivity information and various event counts.

Input fields: graph_time (str): Name of graph = The graph time to get status for.

Output fields: dict: A dictionary containing status information with keys: - status: The overall status (ok, warning, critical, no_monitoring_data) - details: Dictionary with detailed information including: - is_connected: Boolean indicating if graph is connected (Полносвязный граф) - up_node_events: Count of node up events (Восстановление узла) - down_node_events: Count of node down events (Падение узла) - all_host_up_down_events: Count of all host up/down events - network_up_down_events: Count of network up/down events (Падение сети) - adjacency_cost_change_events: Count of adjacency cost change events (изменение стоимости линка) - top_unstable_devices: Top-N [{device, event_count}] sorted desc (самые нестабильные устройства)

Equivalent to GET /graph/{graph_time}/status.

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

Input Schema

NameRequiredDescriptionDefault
graph_timeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds substantive context by enumerating the possible status values (ok, warning, critical, no_monitoring_data) and explaining what each detail field measures. Some of this overlaps with the existing output schema, but the semantic glosses (e.g. adjacency_cost_change_events = link cost change) go beyond structured data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded one-liner is good, but the body repeats itself with a redundant 'Description:' header and a full output-field listing that duplicates the existing output schema. The parenthetical Russian translations add noise for most callers without adding selection or invocation value.

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?

Safety behavior and return shape are adequately covered by annotations and the output schema, but the single required parameter remains undefined in format, and there is no indication of how this differs from sibling status/analysis tools. For a one-parameter read tool this is workable but leaves a real gap at the invocation boundary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 parameter's meaning, and it largely fails: 'graph_time (str): Name of graph = The graph time to get status for' is circular and never states the expected format (timestamp, epoch, identifier, relative window). An agent still cannot construct a valid value with confidence.

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 and resource ('Get the status of a graph') and enumerates what the status contains: connectivity plus event counts. It does not distinguish itself from near neighbors such as get_graph_analysis or get_graph_by_time, so an agent cannot rule those out from the description alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative among the many sibling graph tools. The only implied usage is a generic health/status check, which the agent must infer.

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.