Skip to main content
Glama

get_group_ignored_notifies

Read-only

Retrieves filtered group join requests, including group ID, applicant, inviter, message, and handling status, so you can review ignored membership attempts.

Instructions

获取被过滤的入群请求 Returns: 被过滤的入群请求数组,每项含群号、申请人、邀请人、留言与处理标记。

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": "get_group_ignored_notifies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds useful context by enumerating what each returned item contains (group number, applicant, inviter, message, processing flag). It says nothing about ordering, pagination, volume limits, or permissions, which for an open-world list endpoint are notable omissions.

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 sentences, front-loaded with purpose followed by return shape, with no filler. The 'Returns:' label makes the structure easy to scan, though the return clause could be slightly tighter.

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

Completeness4/5

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

With no output schema and no parameters, the description carries the burden of explaining the result, and it does so by listing the fields of each array item. Missing are result cardinality, ordering, and any prerequisite such as bot-admin rights, which keeps it short of fully complete.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description could add or omit. The schema is trivially complete and the description correctly does not waste words on inputs.

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 gives a specific verb+resource in '获取被过滤的入群请求' (retrieve filtered group-join requests), which is concrete enough for an agent to know what it fetches. It does not, however, contrast itself with the similarly named sibling get_group_ignore_add_request, so the boundary between reading the filtered list and acting on an ignore request is left implicit.

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, when not to, or which sibling handles a related task. The name implies it is a list-getter, so usage is inferable, but nothing actively guides selection against get_group_ignore_add_request or get_group_system_msg.

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