Skip to main content
Glama

list_friend_requests

Read-only

Lists pending friend and group join/invite requests, returning identifiers you can use to approve them via set_friend_add_request or set_group_add_request.

Instructions

Pending friend requests and group join/invite requests seen live, plus the group system message box (入群申请/邀请). Approve with set_friend_add_request / set_group_add_request using the flag.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond them: results reflect live state, the group system message box (入群申请/邀请) is included, and approval is a separate mutating call that consumes the returned flag. It does not cover result shape or any volume/pagination behavior, keeping it below 5.

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 sentences, front-loaded with what is returned and followed by the action to take. Minor waste in the vague 'seen live' phrasing and the redundant bilingual gloss, but nothing that obscures the point.

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?

For a zero-parameter read tool with no output schema, the definition covers the important things an agent needs: what comes back at a high level, that the group system box is included, and that the returned flag feeds the approval tools. The one gap is that the 'flag' field itself is never described as part of the response, leaving the agent to infer where it comes from.

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 there is nothing for the description to disambiguate. Baseline of 4 applies; no parameter claims are made that could mislead.

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?

States a specific verb+resource: lists pending friend requests and group join/invite requests, plus the group system message box. An agent can tell this is a request-inbox reader rather than a friend roster (get_friend_list) or a group roster. It stops short of naming a sibling it is explicitly not, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is implied by the resource name ('pending requests') and the description supplies the follow-up path — approve via set_friend_add_request / set_group_add_request using the flag. There is no explicit statement of when this is preferred over alternatives or any exclusion, so guidance is present but thin.

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