Skip to main content
Glama

Topolograph

get_graph_by_time

Read-onlyIdempotent

Fetch a graph by graph name from Topolograph API. graph name is a string with included date and hours and number of hosts, i.e 01Sep2025_12h44m36s_8_hosts

graph_time (str, optional): The graph time to filter by. Use latest if it's not specified.

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

Input Schema

NameRequiredDescriptionDefault
graph_timeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish this as a read-only, idempotent, non-destructive, open-world fetch, so the safety profile is covered. The description adds the key behavioral detail that the graph identifier encodes date, hours and host count, which explains why callers can't pass an arbitrary name. It says nothing about return contents, size, or not-found behavior, which is where the remaining risk lies.

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?

It is short and front-loaded with the action, and the format example earns its place. The trailing parenthetical '(str, optional)' restates the schema and introduces the required/optional contradiction, which is wasted text that actively misleads.

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?

With no output schema and one parameter, the format explanation covers the main usability gap. Still missing is what a returned graph contains and how 'latest' resolves, which an agent needs to interpret results correctly for a graph-fetching tool.

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

Parameters3/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, and it does provide a concrete format and example, which is the most valuable sentence here. However, it labels graph_time as optional against a required schema field and never mentions the sentinel value 'latest' as an acceptable literal input.

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 gives a specific verb and resource (fetch a graph) plus concrete format guidance for the identifier, including a literal example ('01Sep2025_12h44m36s_8_hosts'). It does not distinguish itself from siblings such as get_all_graphs, get_graph_status or get_graph_analysis, so an agent cannot tell from the text alone which of these retrieves which view.

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?

The only usage hint is 'Use latest if it's not specified', which directly conflicts with the schema marking graph_time as required. There is no guidance on when to pick this tool over sibling graph-retrieval tools, and no note on what happens when the name does not match a graph.

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.