Skip to main content
Glama
Sign In
astral-bridge

astral-bridge

by oines
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

qq_get_recent_messages

Retrieve recent stored QQ messages from a group or private chat. Specify target type, ID, and optional limit or before_message_id.

Instructions

Get recent stored QQ messages for a group or private conversation.

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": {
      "target_type": "<target_type>",
      "target_id": "<target_id>"
    },
    "name": "qq_get_recent_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_typeYes
target_idYes
limitNo
before_message_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Get recent stored QQ messages' without explaining pagination (using before_message_id), ordering, default limit, or whether media is included. The minimal description leaves critical behavioral traits unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but its brevity comes at the cost of completeness. It does not earn its place because it omits essential information for tool invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and 0% parameter description coverage, the description is severely incomplete. It fails to explain pagination, error handling, rate limits, or response format, leaving an AI agent underinformed.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no parameter details. Properties like target_type, target_id, limit, and before_message_id are not explained. The description does not help an agent understand parameter roles beyond their names and types.

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?

Description clearly states verb ('get'), resource ('recent stored QQ messages'), and context ('group or private conversation'). It matches the target_type enum. However, it does not explicitly differentiate from sibling tools like qq_get_message or qq_get_unread_messages, so clarity is slightly reduced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. For example, it does not mention that this tool fetches stored history while qq_get_unread_messages filters unread, or that qq_search_messages is for searching. The description lacks usage context.

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