Skip to main content
Glama

subscribe_events

Subscribe to specified bot event types; matching events enter a buffer for poll_events retrieval, letting AI clients monitor and process runtime events by type or all events.

Instructions

订阅机器人事件流(订阅后匹配事件进入机器人侧环形缓冲,供 poll_events 拉取)。 响应含本次 subscription_id 与当前全部活跃订阅(active_subscriptions)。

Args: types: 事件类型列表(OneBot12 标准类型:"message" / "notice" / "request" / "meta",或 "*" 全部)

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

Input Schema

NameRequiredDescriptionDefault
typesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 it does disclose useful behavior: buffering location (bot side, ring buffer) and the response contents (subscription_id plus all active_subscriptions). It does not say whether subscriptions persist, whether re-subscribing replaces or duplicates an existing subscription, or how the buffer overflows — all relevant for a stateful tool.

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 front-loaded sentences cover the mechanism and the return shape, then a compact Args block covers the only parameter. Nothing is redundant or padded.

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 single-parameter tool with an output schema, the definition covers purpose, mechanism, return fields, and the type vocabulary — enough to call it correctly. The remaining gap is subscription lifecycle (duplicate/replacement behavior and tear-down via the unsubscribe sibling), which is not addressed.

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 description coverage is 0% and the array-of-strings param has no enum, but the description supplies the actual vocabulary ('message'/'notice'/'request'/'meta' or '*' for all), which is genuinely unavailable from the schema. It doesn't explain whether values can be combined or how invalid types are handled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (订阅机器人事件流) and immediately describes the mechanism: matched events go into a bot-side ring buffer for poll_events to fetch. This cleanly separates it from the poll_events sibling, which consumes rather than creates the subscription.

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?

The description establishes the subscribe→poll_events workflow by saying the buffer exists '供 poll_events 拉取', which tells an agent what to do next. It gives no explicit exclusions or mention of the unsubscribe sibling for tear-down, so it stops short of full when/when-not guidance.

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