Skip to main content
Glama

get_doubt_friends_add_request

Read-only

Retrieve suspicious friend requests to review sender details, messages, and request times, helping you identify and handle potential spam or scams.

Instructions

获取可疑好友申请 Returns: 可疑好友申请数组,每项含 uid(作为处理用 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": "get_doubt_friends_add_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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. The description adds the return shape (an array with uid, nickname, source, message and request time), which is genuinely useful since no output schema exists, but it says nothing about the 'count' limit or behavior at zero.

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 compact clauses, purpose first and return shape second, with no filler. The Chinese-only wording is terse but front-loaded and readable.

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 simple read tool with annotations covering safety, the description does cover the return payload, which matters with no output schema. The undocumented 'count' parameter and the absent hint about using uid with the paired set tool leave real gaps.

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

Parameters2/5

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

The single 'count' parameter has 0% schema description coverage (only a default of 50 and minimum 0), so the description must compensate and does not mention it at all. The agent cannot tell whether count caps the number of requests returned or means something else.

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 names a specific verb and resource (获取可疑好友申请) and lists the fields returned, so an agent knows exactly what is retrieved. It does not distinguish itself from the mutation sibling set_doubt_friends_add_request, which is the main clarity gap.

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 explicit statement of when to call this versus the set_doubt_friends_add_request counterpart, nor any prerequisite. The parenthetical that uid is used as a processing flag weakly implies a follow-up write call, but no workflow guidance is given.

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