Skip to main content
Glama

set_group_sign

Performs a group check-in for a specified QQ group using a group ID accessible to the logged-in account.

Instructions

群签到 将 group_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": {
      "group_id": "<group_id>"
    },
    "name": "set_group_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is supplied structurally. The description adds nothing beyond that: it does not say what a check-in produces, whether repeats in the same day fail, or what errors an inaccessible group returns — notable gaps for a non-read operation with open-world reach.

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?

Two short clauses with no filler; the action is front-loaded and the parameter instruction follows. Nothing is redundant, though the content is thin rather than tight.

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?

For a one-parameter, non-read operation with no output schema, the description should at minimum explain the effect of success and the likely failure modes. It covers none of that, leaving the agent with only a label and a parameter substitution hint.

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 description coverage is 100% (group_id is already documented as "群号"), so the schema carries the parameter burden. The description adds one useful semantic constraint — the group must be accessible to the current account — which is meaning beyond the schema, but it is a single clause.

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?

"群签到" names an action (group check-in) on a resource (group), but it is a bare label with no elaboration of what check-in actually entails (points, daily limits, side effects). An agent can guess the gist but cannot tell precisely what the call accomplishes, and no sibling differentiation is offered.

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?

The only guidance is the instruction to substitute group_id with a group number the current account can access — a prerequisite, not a when-to-use rule. There is no statement of when to call this versus other set_group_* tools, nor any exclusion or failure condition.

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