Skip to main content
Glama

onebot_call

Invoke any OneBot v11 or extended QQ action directly by passing an action name and parameters, serving as an escape hatch for capabilities the other tools do not cover.

Instructions

Call any OneBot v11 / extended action of the QQ runtime directly (escape hatch for anything the other tools miss). See list_actions for names.

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

Input Schema

NameRequiredDescriptionDefault
actionYesAction name, e.g. "get_group_member_list"
paramsNoAction parameters
timeout_secondsNoTimeout

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?

The annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds that this is a raw passthrough whose actual behavior is defined by the action argument. It does not warn that some reachable actions mutate or destroy data, nor mention permission/auth requirements or error behavior, which matters for an unconstrained escape hatch.

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 sentences, front-loaded with the core purpose and followed by the discovery hint. The parenthetical slightly interrupts the main clause but nothing is redundant.

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?

For a generic escape hatch with a fully described 3-parameter schema and no output schema, the definition covers what it is, why it exists, and where to find valid action names. The remaining gap is a brief note that return payloads and required params are action-specific.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters are documented in structured form; the description adds only a discovery pointer (list_actions) beyond the schema. It does not explain that `params` must match the selected action's own specification, which is the one non-obvious semantic for a passthrough tool.

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 concrete verb and resource ("Call any OneBot v11 / extended action of the QQ runtime directly") and frames itself as a generic passthrough, which separates it from the specific sibling tools. It does not name a specific sibling it replaces, but the "escape hatch" framing carries the differentiation well enough for an agent to recognize it as the generic fallback.

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?

"escape hatch for anything the other tools miss" gives an explicit condition for choosing this over the specialized tools, and "See list_actions for names" tells the agent how to discover valid values. It stops short of saying when-not to use it (e.g. prefer a dedicated tool when one exists for the action), which is the only missing piece.

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

Deploy Server

Other Tools