Skip to main content
Glama

reload_adapter

Hot-reloads a specified platform adapter by disconnecting and reconnecting its connection, affecting live message flow; requires the allow_adapter_reload config switch to be enabled.

Instructions

热重载指定平台适配器(会断开并重连平台连接,影响在线消息收发)。

受机器人配置 allow_adapter_reload 开关控制,默认禁用;开启后调用才生效。

Args: platform: 平台名

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": {
      "platform": "<platform>"
    },
    "name": "reload_adapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key trait: the connection is dropped and re-established, affecting online message send/receive, plus the config gate. It does not say what happens to in-flight messages or other adapters, what errors appear when the switch is off, or whether the reload is reversible, which matters for a disruptive operation.

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 disruptive-behavior warning is front-loaded, followed by the config gate and then the Args block, so the most decision-relevant information comes first. The 'platform: 平台名' line is near-redundant with the parameter name but is short enough not to be a real cost.

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?

Because an output schema exists, return values need not be explained. However, for a mutation-class tool with no annotations, the definition should say what state is lost during reconnect and how to obtain a valid platform identifier; those gaps remain.

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 coverage is 0% and the only parameter is undocumented in the schema; the description merely glosses 'platform' as 'platform name', adding no format, case rules, valid-value list, or pointer to list_adapters for discovering valid names. For a required identifier this leaves the agent guessing.

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 states a specific verb and resource — hot-reloading a named platform adapter — which is clearly distinct from sibling operations such as reload_module, list_adapters, and get_adapter_status. It does not explicitly name which sibling to use instead, but the action and target are unambiguous.

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?

It gives a real precondition: the call only takes effect when the allow_adapter_reload config switch is on, and it is disabled by default. It also warns that the operation is disruptive to live messaging, which implicitly tells the agent to use it sparingly. It stops short of naming an alternative (e.g. reload_module) for related reload needs.

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