Skip to main content
Glama

reload_module

Reload a specified bot module after code changes without restarting the bot, and return the failure reason if the reload fails.

Instructions

热重载指定模块(改动模块代码后无需重启机器人)。

受机器人配置 allow_module_reload 开关控制(默认允许);重载失败时返回失败原因。

Args: name: 模块名

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does disclose meaningful behavior: the operation is gated by an allow_module_reload config switch (default permitting), and reload failures return a failure reason rather than raising. It stops short of saying whether in-memory module state is reset by the reload, which is the main behavioral risk an agent would want to know.

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 purpose sentence, then the config gate and failure behavior, then a compact Args block. Nothing is padded, though the Args line is somewhat redundant with the parameter's own title.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers the gating condition and failure signaling that the schema does not. For a single-parameter reload operation, the remaining omission — reload format and state-reset semantics — is modest.

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?

There is a single required parameter, and the description's 'name: 模块名' adds the semantic that this is a module name rather than an adapter name or file path, which matters given the sibling reload_adapter. It does not specify the accepted format (identifier vs dotted path).

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 uses a specific verb-and-resource pair in '热重载指定模块' (hot reload the specified module) and adds the outcome of '无需重启机器人' (no bot restart needed), which makes the action concrete. It is reasonably distinguishable from reload_adapter via the '模块' (module) framing, though it never explicitly contrasts the two.

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?

It gives an implied usage context — after changing module code — and notes the allow_module_reload config gate with its default. It does not state when to prefer reload_adapter instead, nor any exclusions or prerequisites such as needing the module already loaded, so guidance is useful but incomplete.

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