Skip to main content
Glama

Reveal contacts

reveal_contacts
DestructiveIdempotent

Returns the WhatsApp, mobile, phone and email of up to 50 businesses, each with its confidence, sources and last-seen date, and a wa.me link for every WhatsApp or mobile so the person can write one to one (their social profiles then show in get_business). Costs 1 credit per new business; businesses already revealed (12 months) and businesses without contacts are not charged. Limit: 500 per day.

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": {
      "codes": "<codes>"
    },
    "name": "reveal_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYesBusiness codes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description earns credit by explaining the actual consequence: credit consumption, the 12-month no-recharge window, and a hard daily limit. It does not explain why the operation is flagged destructive or what happens on partial failure, so it adds real value without fully covering the mutation profile.

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 sentences, front-loaded with the returned data, then the cost/limit constraints — no filler. The first sentence is dense and runs long with several parenthetical asides, slightly hurting scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description takes on the full burden of describing return values and does so precisely, including per-contact confidence, sources, last-seen dates, and wa.me links. Combined with billing, dedupe, and rate-limit disclosure, an agent has everything needed to call this correctly.

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?

There is a single parameter with 100% schema description coverage ('Business codes'), so the schema carries the load. The description only restates the 50-item ceiling already encoded as maxItems and adds no format or batching guidance beyond it, which is the baseline case.

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?

Specific verb and resource ('Returns the WhatsApp, mobile, phone and email of up to 50 businesses') with the exact return payload enumerated (confidence, sources, last-seen date, wa.me links). It is clearly distinguishable from siblings like get_business and my_contacts, which it references as a downstream step.

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 gives concrete operating context: cost of 1 credit per new business, no charge for already-revealed businesses within 12 months or contact-less businesses, and a 500/day cap. What is missing is an explicit when-to-use-vs-alternative statement (e.g., when to call my_contacts or get_business instead), so the routing is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources