Skip to main content
Glama
Sign In

Perisclaw: Use ChatGPT and Claude with your WhatsApp

by com.perisclaw
OverviewDiscussionsAdmin

Get Contacts

contacts_get_batch
Read-only

Resolve a list of JIDs to {name, pushname, lid} in one round trip. Use when chat context has bare JIDs without paired name labels.

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": {
      "contact_ids": "<contact_ids>"
    },
    "name": "contacts_get_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idsYesArray of WhatsApp JIDs to resolve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, destructiveHint false, closed-world). The description adds valuable context beyond them: batch behavior in 'one round trip' and the exact output fields `{name, pushname, lid}`. It does not state what happens for unresolvable JIDs, which prevents a 5.

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 tightly written sentences, with the core purpose and output shape front-loaded and the usage cue following. No sentence is redundant.

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 one-parameter read tool with no output schema, the description supplies the essential missing piece: the return fields and the batching rationale. It could mention behavior for missing/unknown JIDs but is otherwise complete.

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 the single parameter is already documented as an array of WhatsApp JIDs. The description adds only the batch framing ('list of JIDs') and no additional formatting or constraint details, so baseline 3 applies.

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 ('Resolve') and resource ('a list of JIDs') plus the returned shape, which distinguishes it from single-contact siblings like contact_get. It does not explicitly name the sibling alternatives, keeping it below a 5.

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 second sentence gives a concrete triggering condition: use when chat context presents bare JIDs without paired name labels. It lacks explicit exclusions or named alternatives, but the usage context is clear.

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