@kemosoft/mcp-heymax-crm

List Events

heymax_crm_list_events

Read-onlyIdempotent

List customer service events from HeyMax CRM, with optional limit and markdown or JSON response format. Use it to retrieve CRM event data for monitoring or analysis.

Instructions

List customer service events available 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.
`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.1/5.0

Behavior2/5

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

The annotations already declare this as a read-only, open-world, idempotent, non-destructive operation. The description adds no behavioral context beyond that, such as pagination behavior, rate limits, authentication requirements, or the nature of returned events. It does not contradict the annotations, but it also does not enrich them.

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?

The description is a single, front-loaded sentence that states the core purpose without unnecessary detail. The phrase 'available in the HeyMax CRM API' is mildly redundant but not harmful, and no additional sentences are wasted.

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?

The tool has an output schema, rich annotations, and full parameter documentation, so the description does not need to explain return values or safety behavior. Its main purpose statement is sufficient for an agent to identify the tool among siblings, though usage guidance would improve completeness.

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 input schema fully documents the 'limit' and 'response_format' parameters with defaults and constraints. The description adds no parameter meaning beyond what the schema provides, making 3 the appropriate baseline.

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?

The description uses a clear verb ('List') and a specific resource ('customer service events'), which distinguishes it from sibling list tools for pipelines, tags, and lost reasons. However, it does not explicitly differentiate itself from those siblings or clarify the exact scope of 'events'.

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?

The description states what the tool does but gives no guidance on when to use it versus alternatives. It does not mention prerequisites, appropriate contexts, or exclusions.

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

Deploy Server