Skip to main content
Glama

get_adapter_status

Check the runtime status and bot online overview for a specified platform adapter, such as onebot11 or telegram.

Instructions

查询指定平台适配器的运行状态与各 Bot 在线概况。

Args: platform: 平台名(如 onebot11 / telegram)

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": "get_adapter_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose the scope of what comes back (runtime status plus per-Bot online summary), implying a read-only operation, but says nothing about error behavior for an invalid or non-running platform, permissions, or latency/caching.

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?

Two short, front-loaded sentences: the capability first, then the argument meaning. Nothing is wasted, though the phrase about Bot online overview is slightly vague about what fields are included.

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 structure need not be explained, and the single required parameter is documented with examples. For a simple one-parameter status query this is nearly sufficient, with only edge-case behavior left unstated.

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?

Schema coverage is 0%, so the description must compensate, and it does: it names the parameter and gives concrete format examples (onebot11 / telegram), which is meaningfully more than the bare 'Platform' string title in the schema. It still doesn't say whether values are case-sensitive or must come from list_adapters.

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: query (查询) the runtime status of the adapter for a given platform plus each Bot's online overview. This clearly distinguishes it from siblings like list_adapters (enumeration) and reload_adapter (mutation), though it does not name those siblings explicitly.

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?

Usage is only implied: the read-only phrasing suggests checking status, but there is no explicit statement of when to prefer this over list_adapters or get_topology, and no guidance on prerequisites or what to do if the platform is unknown.

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