Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

salvar_cliente

Create or update a client/contact in Ploomes CRM. Use the ID to modify an existing record; include name and other details like address, phone, and custom fields.

Instructions

    Criar ou atualizar um cliente/contato no Ploomes CRM.

    Passe o ID para atualizar um cliente existente.

    Observacoes:
        1. Use buscar_clientes para obter o ID de um cliente existente.
        2. Use buscar_tipos_contato para obter o TypeId (1=Empresa, 2=Pessoa).
        3. Use buscar_cidades para obter o CityId.
        4. Use buscar_segmentos para obter o LineOfBusinessId.
        5. Use buscar_origens_contato para obter o OriginId.
        6. data_nascimento deve estar no formato ISO 8601: "YYYY-MM-DDTHH:MM:SS-03:00"
        7. cnpj e cpf devem ser passados apenas com dígitos, sem formatação.
        8. campos_customizados deve seguir o formato: [{"FieldKey": "chave", "StringValue": "valor"}]
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
cepNo
cpfNo
cnpjNo
nomeYes
emailNo
skypeNo
bairroNo
pais_idNo
tipo_idNo
websiteNo
cargo_idNo
enderecoNo
facebookNo
moeda_idNo
registroNo
telefoneNo
cidade_idNo
estado_idNo
origem_idNo
status_idNo
empresa_idNo
complementoNo
observacoesNo
segmento_idNo
razao_socialNo
chave_externaNo
responsavel_idNo
data_nascimentoNo
departamento_idNo
numero_enderecoNo
telefone_tipo_idNo
relacionamento_idNo
campos_customizadosNo
documento_identidadeNo
numero_funcionarios_idNo
Behavior3/5

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

No annotations provided, so description carries full burden. It states creates/updates based on ID presence, but lacks details on write behavior (e.g., partial vs full overwrite), response output, permissions, or side effects. Moderate transparency.

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?

Front-loaded with purpose, followed by bulleted observations. Efficient without waste. Could improve structure by grouping related parameters, but overall concise and readable.

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 36 parameters, no output schema, and no annotations, the description covers purpose and some prerequisite workflow but omits return value, error handling, and many parameter details. Adequate but has clear gaps.

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 coverage is 0%, but description adds meaning for a few parameters via observations (e.g., tipo_id, cidade_id, data_nascimento, cnpj, cpf, campos_customizados). However, many of the 36 parameters (e.g., skype, facebook, website) are unexplained. Partial compensation; missing many.

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?

Description clearly states the tool creates or updates a client/contact in Ploomes CRM, distinguishing it from sibling tools like excluir_cliente, buscar_clientes, etc. The verb+resource is specific.

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?

Eight observations explicitly list prerequisites and when to use other tools (e.g., buscar_clientes for ID, buscar_tipos_contato for TypeId) and format requirements for data_nascimento, cnpj, cpf, campos_customizados. Provides excellent guidance for correct invocation.

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/JoseAlmeida-Ploomes/ploomes-mcp'

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