@kemosoft/mcp-heymax-crm

Find Services by Phone

heymax_crm_find_services_by_phone

Read-onlyIdempotent

Find existing HeyMax CRM service records by phone number, grouped by CPF, to identify customer history and linked services. Returns results in markdown or JSON.

Instructions

Find existing customer service records by phone number, grouped by CPF in the HeyMax CRM API.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of items to return, between 1 and 100.
`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
`count`	Yes
`items`	Yes
`truncated`	Yes
`total_count`	Yes

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, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful detail that results are grouped by CPF, but says nothing about pagination behavior, result limits, or auth requirements beyond the annotation set.

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 wasted words, but it is terse enough that it omits any usage or behavioral detail that would have earned the space.

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-value explanation is not required, and annotations cover safety. However, for a search tool whose siblings share overlapping phone/CPF semantics, the description leaves selection criteria and result-shaping (grouping, limits) under-explained.

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 coverage is 100%, so all three parameters (phone, limit, response_format) are already documented in the schema. The description only echoes the phone filter and adds no syntax, format, or default-value nuance beyond structured data; baseline 3 is appropriate.

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 ('Find'), resource ('customer service records'), and filter ('by phone number'), plus the grouping behavior by CPF. It is distinguishable from siblings like validate_phone or get_service_status_by_id, though it does not name them explicitly.

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?

No when-to-use guidance is given, and no alternative is named. An agent must infer on its own that this differs from heymax_crm_validate_phone or heymax_crm_get_service_status_by_funnel_and_cpf, both of which also take phone/CPF input.

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

Deploy Server