Skip to main content
Glama

list_adapters

Lists registered platform adapters with status and bot online state so you can confirm the target platform before sending messages.

Instructions

列出机器人已注册的平台适配器及状态(status: started/stopped/disabled,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": "list_adapters"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It discloses the status vocabulary and the online-state meaning, which is useful beyond the schema, but it never explicitly states that the call is side-effect free or whether disabled adapters are included. Read-only behavior is only implied by the verb 'list'.

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 first front-loads what is returned and its status vocabulary, the second gives the calling context. No redundant restatement of the name or filler.

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 and the description needn't explain return values, yet it still summarizes the key status field. For a zero-parameter listing tool this is close to sufficient; only the boundary with get_adapter_status and the absence of an explicit read-only statement leave a small gap.

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 to explain; baseline for a parameterless tool applies. The description does not invent or misuse parameter semantics.

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 names a specific verb and resource (list the bot's registered platform adapters) and enumerates the status values it reports (started/stopped/disabled, plus Bot online state). It stops short of distinguishing itself from a similarly named sibling such as get_adapter_status, so an agent reading only the text cannot fully rule that alternative out.

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 an explicit use case: call this before sending a message to confirm the target platform name and online status. That is concrete and actionable. It does not state when not to use it or point at the sibling tools that return single-adapter status, so the guidance is clear but not exhaustive.

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