@kemosoft/mcp-heymax-crm

Validate Phone

heymax_crm_validate_phone

Read-onlyIdempotent

Check whether a phone number exists on WhatsApp using the HeyMax CRM API. Provide a phone number to verify WhatsApp availability.

Instructions

Validate whether a phone number exists on WhatsApp according to the HeyMax CRM API.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`phone`	Yes	Phone number with or without punctuation.
`response_format`	No	Response format. Use 'markdown' for readability or 'json' for structured output.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`input`	Yes
`result`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one useful fact beyond them: validation is performed against WhatsApp through the HeyMax CRM API, i.e. an external system. It still omits what a positive/negative result means, rate limits, or cost.

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?

A single front-loaded sentence with no waste and no redundancy. The trailing clause about the HeyMax CRM API is slightly ceremonial but still conveys the external source.

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

Completeness3/5

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

An output schema exists so return values need no explanation, and both parameters are schema-documented. What is missing is routing context versus find_services_by_phone and any statement of what constitutes a valid result.

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%, and the description adds nothing about phone formatting (E.164, country code) or response_format beyond what the schema already states. Baseline 3 applies when the schema carries the parameter detail.

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 (Validate) and resource (phone number on WhatsApp), which is unambiguous. However, it never differentiates itself from the sibling heymax_crm_find_services_by_phone, which also takes a phone and could be confused at selection time.

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

Usage Guidelines2/5

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

There is no guidance on when to reach for this tool: no mention that it should be used before a WhatsApp outreach, no condition that selects it over find_services_by_phone, and no exclusions. Usage is only implicit from the verb.

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

Deploy Server