Skip to main content
Glama
Sign In
astral-bridge

astral-bridge

by oines
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

qq_get_message

Retrieve a stored QQ message using its OneBot message ID. Input the message ID to fetch the corresponding message from history.

Instructions

Get one stored QQ message by OneBot message_id.

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": {
      "message_id": "<message_id>"
    },
    "name": "qq_get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes
target_typeNo
target_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only says 'get'. It fails to disclose read-only nature, return structure, error handling, or whether the message must be previously stored by the bot. Minimal transparency.

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?

The description is a single concise sentence with no wasted words. It is front-loaded with the verb and object. However, brevity comes at the cost of missing critical details.

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

Completeness2/5

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

Given three parameters and no output schema, the description is severely incomplete. It omits return format, optional parameter roles, and any preconditions, leaving the agent underinformed for correct invocation.

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 coverage is 0%; the description adds no meaning to parameters. It ignores target_type and target_id, leaving their purpose ambiguous given only message_id is required. The agent has no clue how to use optional params.

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 clearly states it retrieves a stored QQ message by OneBot message_id, which distinguishes it from sibling tools that list or search messages. However, it could be more specific about the scope (e.g., 'single message').

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 is provided on when to use this tool versus alternatives like qq_search_messages or qq_get_recent_messages. The agent receives no context about prerequisites or preferred scenarios.

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