Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Find Minimax Contacts By E-mail

minimax_find_contacts_by_email
Read-onlyIdempotent

Find contact persons by email across all customers to identify the customer an incoming email belongs to; returns matching contacts with customer references.

Instructions

Find contact persons by e-mail address across all customers -- the way to get from an incoming e-mail to the customer it belongs to.

Returns: str: JSON SearchResult of contacts, each with its Customer reference.

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": {
      "params": "<params>"
    },
    "name": "minimax_find_contacts_by_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the extra bar is low. The description adds the meaningful scope fact that the search spans all customers rather than a single record, and that every hit carries a Customer reference. It says nothing about whether the match is exact or partial, or what happens when several contacts share an address.

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 front-loaded sentences state purpose and scope with no waste. The 'Returns:' block is partly redundant since an output schema exists, though it does at least name the Customer reference the caller cares about.

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?

With a rich annotation set and an output schema, the description only needs to establish purpose and scope, which it does. The remaining gap is behavioural detail around match semantics and organisation scoping, a moderate rather than critical omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported at 0% and the description compensates for none of it — it never mentions the e-mail input's expected format, the organisation_id scoping (which qualifies the 'across all customers' claim), or pagination/sorting controls. An agent gets no help from the prose on how to shape the call.

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 and resource ('Find contact persons by e-mail address') with an explicit scope ('across all customers'), and frames the real-world intent (mapping an incoming e-mail to its customer). It doesn't explicitly differentiate itself from any sibling lookup tool, which keeps it off 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 clause 'the way to get from an incoming e-mail to the customer it belongs to' gives a concrete when-to-use context that would let an agent pick this tool for the e-mail-to-customer routing case. There is no when-not guidance and no named alternative (e.g. for lookup by name or tax number), so it stops short of full routing guidance.

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