Skip to main content
Glama
FengSui 4G/5G Router MCP Server

FengSui 4G/5G Router MCP Server

Search the Contact Book

search_contacts
Read-onlyIdempotent

Search an encrypted contact book by name, note, or number to retrieve matching contacts and their numbers, so you can find a number before checking or sending a message.

Instructions

Search FengSui's encrypted contact book by name, note or number and return the matching contacts with their numbers. Use it to find a number before checking or sending a message. Reads FengSui's own records, not the router.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMost contacts to return, 1 to 50 (default 20).
queryNoPart of a name, note or number to look for; empty lists every contact.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.9.5
    • changedInput schema / properties / limit / description
      Previous value: -"1..50 (default 20)."New value: +"Most contacts to return, 1 to 50 (default 20)."
    • addedInput schema / properties / query / description
      Added value: +"Part of a name, note or number to look for; empty lists every contact."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds context the annotations do not: the data is encrypted, it lives in FengSui's own store rather than the router, and results include contact numbers — useful for deciding whether this is the right data source. Pagination/total-count behavior is left unmentioned but the limit parameter is documented.

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 with zero filler; the core action and searchable fields come first, and the data-source clarification follows. Every clause carries information an agent would use.

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 two-parameter, zero-required read tool with no output schema, the description covers what is searched, what is returned, and where the data comes from — enough to call it correctly. A note on ordering or result truncation would round it out but is not essential.

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%, so both parameters are fully documented in the schema and the baseline is 3. The description's 'by name, note or number' and 'empty lists every contact' (in the schema) reinforce query semantics but add little beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) plus resource (FengSui's encrypted contact book), the searchable fields (name, note, number), and what comes back (matching contacts with their numbers). The clause 'Reads FengSui's own records, not the router' separates it from the router-oriented siblings without needing a named alternative.

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?

'Use it to find a number before checking or sending a message' gives a concrete usage context that ties the tool to downstream actions. There is no explicit when-not clause or named alternative, but that is a minor gap given the narrow, read-only scope.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.