Skip to main content
Glama
Expert-Integrado

Conexa MCP

PATCH /customer/:id (Customer)

update_customer

Update customer data in the Conexa system, modifying fields like contact, address, tax deductions, and personal or legal information for individual or business clients.

Instructions

Edição de uma ou n informações de um cliente no sistema Conexa.

Campos do body:

  • companyId (integer): Id da unidade

  • name (string): Nome do cliente

  • tradeName (string): Nome fantasia

  • pronunciation (string): Pronúncia

  • fieldOfActivity (string): Ramo de atividade

  • notes (string): Observações

  • cellNumber (string): Celular

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

  • website (string): Site

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

  • login (string): Login da área do cliente

  • password (string): Senha da área do cliente

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

  • notesNfse (string): Observações da NFS-e (depende de configuração)

  • 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): CPF

  • naturalPerson.rg (string): RG

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

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

  • naturalPerson.profession (string): Profissão

  • naturalPerson.maritalStatus (string): 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): CNPJ

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

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

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

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

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

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

  • foreign.profession (string): Profissão

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

  • address.zipCode (string): CEP

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

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

  • address.city (string): Cidade

  • address.street (string): Logradouro

  • address.number (string): Número

  • address.neighborhood (string): Bairro

  • address.additionalDetails (string): Complemento

  • 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): 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): Nome do plano de internet (Disponível apenas com o módulo Mikrotik ativo)

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

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

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

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

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

  • mailingAddress.zipCode (string): CEP

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

  • mailingAddress.city (string): Cidade

  • mailingAddress.street (string): Logradouro

  • mailingAddress.number (string): Número

  • mailingAddress.neighborhood (string): Bairro

  • mailingAddress.additionalDetails (string): Complemento

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

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesValor de :id na rota /customer/:id
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 declare readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond the field list. It does not explain that unprovided fields remain unchanged (implied by PATCH), or mention required permissions, side effects, or error conditions.

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

Conciseness2/5

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

The description is excessively long (over 50 lines) and structured as a flat bullet list without clear separation between nested objects (e.g., naturalPerson, legalPerson). It reads like a dump of the API documentation rather than a concise tool definition.

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?

Given the complexity of nested objects and numerous optional fields, the description covers most field details but omits information about return values, idempotency, or error handling. No output schema is provided, so the agent knows the input structure but not what to expect back.

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?

The input schema only defines id and body with minimal descriptions. The tool description compensates by providing a comprehensive list of body fields with types, formats, and examples (e.g., date format 'yyyy-MM-dd', enum values for maritalStatus). However, it does not indicate which fields are required within the body.

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 'Edição de uma ou n informações de um cliente' which clearly indicates updating customer information. The title 'PATCH /customer/:id (Customer)' reinforces this. It distinguishes from siblings like create_customer and get_customer, but could be more explicit about the scope.

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 guidance on when to use this tool versus alternatives such as create_customer or delete_customer. It does not mention prerequisites, such as the customer must already exist, or when a partial update is appropriate versus a full replacement.

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