Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

salvar_venda

Create or update a sales order in Ploomes CRM by providing a deal ID and optional details like products, discounts, and commissions.

Instructions

    Criar ou atualizar um pedido/venda no Ploomes CRM.

    Passe o ID para atualizar um pedido existente.

    Observacoes:
        1. Use buscar_negocio para obter o DealId.
        2. Use buscar_clientes(tipo=EMPRESA) para o ContactId e buscar_clientes(tipo=PESSOA) para o PessoaId.
        3. Use buscar_vendas_config para obter o StageId e TemplateId.
        4. agente_id é o ID do representante comercial vinculado à venda.
        5. comissao_percentual é o percentual de comissão do agente (ex: 5.0 para 5%).
        6. produtos deve seguir o formato: [{"ProductId": 1, "Quantity": 2, "UnitPrice": 100.0}]
        7. campos_customizados deve seguir o formato: [{"FieldKey": "chave", "StringValue": "valor"}]
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
valorNo
tituloNo
descontoNo
etapa_idNo
moeda_idNo
produtosNo
agente_idNo
descricaoNo
pessoa_idNo
contato_idNo
negocio_idYes
template_idNo
chave_externaNo
responsavel_idNo
campos_customizadosNo
comissao_percentualNo
comentarios_internosNo
Behavior2/5

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

The description reveals only that the tool creates or updates, implying mutation, but gives no details on idempotency, error behavior, destructive potential, or authentication requirements. With no annotations, this lack of behavioral context is a significant gap for a mutation tool.

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?

The description is concise, with a front-loaded purpose statement followed by a bulleted list of observations. It packs useful information without unnecessary verbosity, though the list could be better organized by grouping prerequisites vs. parameter formats.

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 tool's complexity (18 parameters, no output schema, no annotations), the description provides decent coverage for input usage but omits return value details, error handling, and behavioral traits like idempotency. It is moderately complete but leaves several contextual 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%, so the description partially compensates by explaining the format for produtos and campos_customizados, and the meaning of agente_id, comissao_percentual, and negocio_id. However, many parameters (e.g., valor, titulo, desconto, etapa_id) are left without additional semantics beyond their names.

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 clearly states it creates or updates a sale/order in Ploomes CRM and specifies that passing an ID triggers an update. This distinguishes it from general CRUD tools, but it does not explicitly differentiate from siblings like 'salvar_negocio' or 'salvar_proposta'.

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 description includes seven explicit observations detailing prerequisite lookups for Deald, Contact, Stage, Template, etc. This provides strong context for when to use the parameters. However, it does not mention when not to use this tool or contrast it with alternative tools among siblings.

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