Radar noEixo

Create contact

create_contact

Cria um contato no CRM. Procure ANTES com list_contacts ou get_contact: criar com um telefone que já existe gera duplicata. Para só mudar estágio/status de quem já existe, use update_contact_status.

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": {
      "name": "<name>",
      "phone": "<phone>"
    },
    "name": "create_contact"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Nome do contato
`email`	No	E-mail (opcional)
`notes`	No	Anotação inicial (opcional)
`phone`	Yes	Telefone com código do país, ex: 5511999999999
`source`	No	Origem do contato, ex: whatsapp, manual, indicacao
`status`	No	Status inicial (padrão: lead)
`company`	No	Empresa (opcional)
`document`	No	CPF (pessoa física, 11 dígitos) ou CNPJ (empresa, 14 dígitos), com ou sem pontuação (opcional). Vai para o cadastro que o agente mostra ao cliente no WhatsApp para confirmar.
`dealValue`	No	Valor estimado do negócio (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare a non-read-only, non-destructive write. The description adds the key behavioral fact those annotations cannot convey: creating with an existing phone produces a duplicate record, which is why the lookup step exists. It stops short of saying what is returned or whether creation can be undone, but the highest-value side effect is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: purpose first, then the dedupe warning and required lookup, then the routing alternative. Nothing is redundant and no sentence could be dropped without losing guidance.

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?

For a 9-parameter create tool whose schema is fully documented and which has no output schema, the description covers the risk (duplication) and the routing decision. Only the return value after creation is unmentioned, which is a minor gap rather than a blocker.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning to the phone parameter by revealing it acts as the dedupe key. It also implies status is separate from a pipeline stage, mirroring the update_contact_status split. Other parameters are left entirely to the schema.

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?

"Cria um contato no CRM" is a specific verb + resource, and the description immediately separates this tool from list_contacts, get_contact and update_contact_status by name. An agent can distinguish it from every sibling without opening a schema.

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

Usage Guidelines5/5

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

It states a mandatory pre-condition (search first with list_contacts or get_contact) and names an explicit alternative with its selecting condition (to only change stage/status, use update_contact_status). Both when-to-use and when-not-to-use are present.

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

All Radar noEixo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?