Skip to main content
Glama

get_topology

Retrieve bot runtime topology covering module command, event handler, and route ownership plus adapter and bot status and scope bindings.

Instructions

获取机器人运行时拓扑(模块的命令/事件处理器/路由归属、适配器与 Bot 状态、作用域绑定)。 已脱敏:不包含绝对路径与密钥类字段。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_topology"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral value by disclosing that output is sanitized — no absolute paths or secret-type fields — and that this is a read-style snapshot of runtime state. It says nothing about cost, permissions, or freshness of the snapshot, which matters for a full-topology call.

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

Conciseness5/5

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

Two short sentences: the payload scope first, the sanitization caveat second. No filler, no restatement of the name, and the most decision-relevant content leads.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters and an output schema present, the description only needs to convey scope and behavior, and it does both, including the sanitization guarantee. The one gap is routing guidance relative to the many narrower status/list siblings.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline of 4 applies. The schema is an empty object and the description correctly avoids redundant parameter talk.

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 (获取机器人运行时拓扑) and enumerates the concrete contents: module command/event handlers, route ownership, adapter and Bot status, and scope bindings. That enumeration implicitly separates it from narrow siblings like get_adapter_status or list_modules, though no sibling is named explicitly.

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 sentence telling the agent when to pick this over get_adapter_status, list_modules, or get_module_info, and no exclusions or prerequisites. Breadth of content is only inferable from the enumerated fields, not stated as a usage rule.

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