Skip to main content
Glama

set_diy_online_status

Configure a custom QQ online status by choosing a status face and optional wording, letting users display the presence they want.

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": {
      "face_id": "<face_id>"
    },
    "name": "set_diy_online_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
face_idYes
wordingNo
face_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false, destructiveHint=false, so the mutation profile is partially covered. Beyond that, the description adds nothing: no indication of what the custom status persists, how long it lasts, whether it requires login, or what happens on failure — notable for an open-world write operation.

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?

It is a single short sentence with no filler, so nothing is wasted. But brevity here comes at the cost of substance rather than from disciplined editing.

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?

This is a non-read-only, open-world mutation tool with three undocumented parameters and no output schema. Given that complexity and the 0% schema coverage, the description is far too thin for an agent to invoke it confidently.

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 three parameters (face_id, wording, face_type) and the description does not mention any of them. Terms like 'face_id' and 'face_type' are opaque without explanation, so the definition gives no meaning beyond parameter names alone.

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

Purpose3/5

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

The description states a verb and resource ('设置自定义在线状态' / set custom online status), so the general purpose is identifiable. However, it does not distinguish this from the sibling 'set_online_status' — an agent cannot tell what makes this status 'custom' or which of the two to pick.

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?

There is no when-to-use, when-not-to-use, or prerequisite information. The presence of a very similar sibling ('set_online_status', plus 'set_input_status' and status getters) makes the absence of routing guidance a real problem.

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