Skip to main content
Glama
Expert-Integrado

Conexa MCP

POST /customer (Customer)

create_customer

Create a customer in Conexa, including personal or legal entity details, address, contacts, login access, and tax deduction settings.

Instructions

Criação de um cliente no sistema Conexa. ⚠ Fique atento ao produto do seu sistema. Há campos que não são necessários!

Campos do body:

  • companyId (integer) [obrigatório]: ID da unidade

  • name (string) [obrigatório]: Nome do cliente

  • tradeName (string / null): Nome fantasia

  • pronunciation (string / null): Pronúncia

  • fieldOfActivity (string / null): Ramo de atividade

  • notes (string / null): Observações

  • cellNumber (string / null): Celular

  • website (string / null): Site

  • hasLoginAccess (boolean): Tem acesso a área do cliente

  • login (string / null) [obrigatório]: Login da área do cliente

  • password (string / null) [obrigatório]: Senha da área do cliente

  • automaticallyIssueNfse (string / null): Emitir NFS-e automaticamente. A opção deve ser uma das seguintes: whenGeneratingBilling , afterPaymentBilling , notIssue

  • notesNfse (string / null): Observações da NFS-e

  • taxDeductions (object): Retenção de Imposto Municipal e Federal

  • taxDeductions.iss (boolean): Retém ISS (Imposto Municipal)

  • taxDeductions.ir (boolean): Retém IR (Imposto Federal)

  • taxDeductions.pis (boolean): Retém PIS (Imposto Federal)

  • taxDeductions.inss (boolean): Retém INSS (Imposto Federal)

  • taxDeductions.csll (boolean): Retém CSLL (Imposto Federal)

  • taxDeductions.cofins (boolean): Retém COFINS (Imposto Federal)

  • naturalPerson (object): Objeto com os dados referentes a um cliente Pessoa Física

  • naturalPerson.cpf (string / null): CPF

  • naturalPerson.rg (string / null): RG

  • naturalPerson.birthDate (date): Data de aniversário. Formato: yyyy-MM-dd

  • naturalPerson.issuingAuthority (string / null): Órgão expedidor

  • naturalPerson.profession (string / null): Profissão

  • naturalPerson.maritalStatus (string / null): O estado civil do cliente, sendo: " married ", " single ", " divorced ", " widowed " ou " not informed "

  • legalPerson (object): Objeto com os dados referentes a um cliente Pessoa Jurídica

  • legalPerson.cnpj (string / null): CNPJ

  • legalPerson.foundationDate (date): Data de fundação. Formato: yyyy-MM-dd

  • legalPerson.stateInscription (string / null): Inscrição estadual

  • legalPerson.municipalInscription (string / null): Inscrição municipal

  • foreign (object): Objeto com os dados de estrangeiro

  • foreign.document (string / null): Número do documento de identificação estrangeiro

  • foreign.birthDate (date): Data de aniversário. Formato: yyyy-MM-dd

  • foreign.profession (string / null): Profissão

  • address (object): Objeto com o endereço do cliente

  • address.zipCode (string / null): CEP

  • address.country (string / null): País de origem (apenas se for estrangeiro )

  • address.state (string / null): Sigla do estado (UF)

  • address.city (string / null): Cidade

  • address.street (string / null): Logradouro

  • address.number (string / null): Número

  • address.neighborhood (string / null): Bairro

  • address.additionalDetails (string / null): Complemento

  • phones (string[]): Array com os telefones de contato. Os telefones devem ter 10 ou 11 números.

  • emailsMessage (string[]): Array com os e-mails para envio de recados

  • emailsFinancialMessages (string[]): Array com os e-mails para envio de avisos financeiros

  • tagsId (integer[]): Array com os IDs das Tags para associar ao cliente

  • extraFields (array of objects): Array de objetos de Campos Extras

  • extraFields[].id (integer) [obrigatório]: ID do Campo Extra

  • extraFields[].value (string): Valor para o Campo Extra

  • isNetworkingProfileVisible (boolean): Exibir perfil do cliente na área de Networking da área do cliente

  • isBlockedBookingCustomerArea (boolean): Não permite que o cliente cadastre novas reservas pela área do cliente, caso hasLoginAccess seja true

  • isAllowedBookingOutsideBusinessHours (boolean): Permite reservar fora do horário de funcionamento padrão, caso hasLoginAccess seja true

  • internetPlan (string / null): Nome do plano de internet (Disponível apenas com o módulo Mikrotik ativo)

  • businessPresentation (string / null): Breve apresentação sobre o cliente

  • offeredServicesProducts (string / null): Serviços e produtos oferecidos

  • receptionOrientations (string / null): Orientações para atendimento

  • mailingOrientations (string / null): Orientações para correspondência

  • mailingAddress (object): Objeto com o endereço para correspondências

  • mailingAddress.zipCode (string / null): CEP

  • mailingAddress.state (string / null): Sigla do estado (UF)

  • mailingAddress.city (string / null): Cidade

  • mailingAddress.street (string / null): Logradouro

  • mailingAddress.number (string / null): Número

  • mailingAddress.neighborhood (string / null): Bairro

  • mailingAddress.additionalDetails (string / null): Complemento

  • mailingAddress.landmark (string / null): Ponto de referência

  • extensionNumbers (string[]): Array com os ramais

  • defaultDueDay (integer): Dia de vencimento padrão do cliente

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesCorpo JSON da requisição (campos na descrição da tool)
Behavior2/5

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

Annotations indicate it is not read-only (write operation) and not destructive. The description does not add behavioral details beyond field listing, such as authentication needs or side effects.

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

Conciseness3/5

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

The description is very long and contains a wall of text listing all fields. While it has some structure with indentation, it is not concise and buries the essential purpose.

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 complex tool with many nested objects, the description is complete in documenting all fields. However, it lacks broader context about expected usage or outcomes, though no output schema exists to cover return values.

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

Parameters5/5

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

With a minimal input schema, the description provides exhaustive parameter semantics including types, required flags, formats, and enumerated values, fully compensating for the schema's lack of 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?

The description states it creates a customer in the Conexa system, which is clear. However, it does not differentiate from sibling tools like create_person or create_potential_customer.

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 warns about unnecessary fields but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or constraints.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Expert-Integrado/conexa-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server