Skip to main content
Glama

set_self_longnick

Sets your QQ profile signature from a provided string so AI-driven account management can update longNick/long_nick values.

Instructions

设置个性签名(longNick/long_nick,严格 string)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_self_longnick"
  }
}

Input Schema

NameRequiredDescriptionDefault
longNickNo
long_nickNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive nature is covered by structured data. Beyond that, the description says nothing about effects: no length limits, no rate limiting, no statement that the previous signature is overwritten, no indication of what is returned. For a mutation tool this is a notable gap.

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?

A single front-loaded clause with no filler. The only redundancy is the '严格 string' type assertion, which the input schema already declares.

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

Completeness3/5

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

For a two-parameter mutation tool with no output schema, the essentials (verb, resource, field names, type) are present. What is missing is the resolution rule for the duplicated parameter and any constraint on the input value, both of which an agent would need to call it reliably.

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

Parameters3/5

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

Schema coverage is 0% and both parameters are optional strings, so the description must compensate. It does add real meaning by naming both keys and asserting the value is a strict string, implying longNick and long_nick are aliases for the same field. However, it never says which alias takes precedence when both are supplied, nor any length or format constraints.

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 states a specific verb+resource ('设置个性签名'), which is unambiguous and distinguishes it from sibling setters such as set_group_card or set_friend_remark that target other resources. The parenthetical identifiers (longNick/long_nick) further pin down the exact field being written, though it never says whether this signature belongs to the calling account or someone else.

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 statement of when to use this tool, no prerequisites (e.g. login state or permissions), and no mention of alternatives for setting profile text. The only guidance is the field-name hint, which is not usage guidance.

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