Skip to main content
Glama

set_input_status

Set a QQ user's chat input status, such as typing, to signal activity before sending messages. Provide the target user ID and optional event type.

Instructions

设置输入状态

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": {
      "user_id": "<user_id>"
    },
    "name": "set_input_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes
event_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

The annotations declare a non-read-only, open-world operation, so this is a mutation with external effect, yet the description says nothing about what gets changed, what permissions or login state are required, or what happens on failure. It adds zero context beyond the annotations and leaves the side effects of a write call completely opaque.

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

Conciseness2/5

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

It is brief, but this is under-specification rather than conciseness: a four-character phrase with no front-loaded verb-object framing, scope, or any detail an agent could act on.

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?

For a mutation tool with two undocumented parameters, no output schema, and only hint-level annotations, the description should explain the target user, the event_type domain, and the effect of the call. None of that is present, so the definition is not callable with confidence.

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% for both parameters, so the description carries the full burden — and it provides nothing. Neither user_id (integer or string, minimum 1) nor event_type (integer, default 0) is explained; the meaning and valid values of event_type are entirely undocumented anywhere.

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

Purpose2/5

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

"设置输入状态" restates the tool name (set_input_status) with no additional specificity — it does not say whose input status, on which platform, or what an "input status" actually is. It also does nothing to distinguish itself from near-identical siblings such as set_online_status or set_diy_online_status.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no preconditions, and no mention of when to prefer this over the many set_*_status siblings. An agent must guess entirely from the name.

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