Skip to main content
Glama

find_contact

Read-only

Search friends by remark, nickname, or QQ number and groups by name or number, then return qq: or group: targets for messaging or group actions.

Instructions

Search friends (by remark, nickname or QQ number) and groups (by name or number). Returns ids to use as targets ("qq:" / "group:").

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": {
      "query": "<query>"
    },
    "name": "find_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoLimit to friends or groupsall
limitNoMax results
queryYesName or number fragment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already establish that this is a non-destructive, open-world read, so the safety profile is covered. The description's real addition is the return contract — prefixed id strings usable as targets — which matters since there is no output schema. It says nothing about result ordering, partial/fuzzy matching behavior, or what an empty result looks like, which limits it to adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the scope stated first and the return-value contract second. Every phrase carries information an agent needs before calling.

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 three-parameter lookup with no output schema, the definition covers what is searched, how to narrow it, and the shape of the returned ids. The remaining gap is behavioral detail on matching and result ordering, which is minor but not nothing for a search tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: it names the specific searchable fields (remark, nickname, QQ number for friends; name or number for groups), which is more concrete than the schema's generic 'Name or number fragment'. It also implicitly explains the kind enum's effect by pairing each resource with its matchable attributes.

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 opens with a concrete verb+resource pair ('Search friends ... and groups') and enumerates the matchable fields (remark, nickname, QQ number / name, number), so an agent knows exactly what this tool retrieves. It does not explicitly contrast itself with any sibling, but among the supplied siblings it is the only lookup-style tool, making the role unambiguous in practice.

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

Usage Guidelines4/5

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

The clause 'Returns ids to use as targets' tells the agent the downstream purpose: this is the discovery step that produces the 'qq:<id>' / 'group:<id>' values other tools need. That is clear affirmative guidance, though there is no explicit statement of when not to use it or what to do if no results are returned.

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