Skip to main content
Glama
Sign In

Perisclaw: Use ChatGPT and Claude with your WhatsApp

by com.perisclaw
OverviewDiscussionsAdmin

Search Contacts

search_contacts
Read-only

Fuzzy-match a contact by name, or find the contact an exact email address belongs to (its contact_id is also their WhatsApp chat). Handles typos, phonetic variants, and word-order swaps.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results. Default 10.
queryYesName or fragment to search for, or an email address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a safe read-only, non-destructive, closed-world operation, and the description adds useful behavioral context: typo tolerance, phonetic matching, word-order swaps, and that contact_id doubles as the WhatsApp chat identifier. It does not cover rate limits, pagination, or full return shape, so it is strong but not exhaustive.

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?

The description is one dense, front-loaded sentence with zero waste. It puts the primary search modes first and uses its trailing clause to add matching behavior efficiently.

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 read-only search tool with full schema coverage and annotations, the description covers purpose, query modes, and matching behavior well enough to invoke it correctly. It does not describe result shape or sorting, but no output schema exists to require that detail.

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?

With 100% schema coverage, the schema already documents both parameters. The description still adds meaning by clarifying that name/fragment queries are fuzzy-matched while email lookups are exact and resolve to a specific contact.

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?

The description states specific operations: fuzzy contact matching by name and exact email-to-contact lookup. It clearly distinguishes the search behavior from a direct contact lookup such as contact_get by emphasizing fuzzy matching and the email-based path.

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?

It clearly explains the two usage modes: use a name fragment for fuzzy matching, or an email address for exact lookup. It does not explicitly name alternatives like contact_get or state when not to use this tool, which keeps it below a 5.

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

All Perisclaw: Use ChatGPT and Claude with your WhatsApp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources