Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

salvar_proposta

Create or update proposals in Ploomes CRM. Provide a deal ID to generate a quote with products, pricing, and custom fields.

Instructions

    Criar ou atualizar uma proposta/cotacao no Ploomes CRM.

    Passe o ID para atualizar uma proposta existente.

    Observacoes:
        1. Use buscar_negocio para obter o DealId.
        2. Use buscar_clientes(tipo=EMPRESA) para obter o ContactId e buscar_clientes(tipo=PESSOA) para o PessoaId.
        3. Use buscar_templates_documentos para obter o TemplateId.
        4. data_validade deve estar no formato ISO 8601: "YYYY-MM-DDTHH:MM:SS-03:00".
        5. produtos deve seguir o formato: [{"ProductId": 1, "Quantity": 2, "UnitPrice": 100.0}]
        6. campos_customizados deve seguir o formato: [{"FieldKey": "chave", "StringValue": "valor"}]
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
notasNo
valorNo
tituloNo
descontoNo
moeda_idNo
produtosNo
descricaoNo
pessoa_idNo
contato_idNo
negocio_idYes
template_idNo
valor_freteNo
chave_externaNo
data_validadeNo
prazo_entregaNo
responsavel_idNo
forma_pagamentoNo
numero_parcelasNo
modalidade_freteNo
campos_customizadosNo
Behavior3/5

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

No annotations are present, so the description carries full burden. It discloses format requirements (ISO 8601 for data_validade, array formats for produtos and campos_customizados) but lacks details on side effects, permissions, or whether updates are full replacements.

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 and uses a bulleted list for observations, making it scannable. However, it could better separate main purpose from detailed prerequisites.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given high complexity (21 parameters, no output schema, no annotations), the description is incomplete. It does not explain return values or behavior of many parameters, leaving significant gaps for the agent.

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

Parameters2/5

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

With 0% schema coverage, the description must compensate. It explains only a few parameters (id, negocio_id, data_validade, produtos, campos_customizados) but ignores 16 others (e.g., notas, valor, titulo, desconto, moeda_id). Most parameters lack any explanation.

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?

The description clearly states the tool creates or updates a proposal/quote in Ploomes CRM. It distinguishes from sibling tools like buscar_proposta (search) and excluir_proposta (delete).

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 explains when to provide an ID for updates and lists prerequisites (buscar_negocio, buscar_clientes, buscar_templates_documentos). It provides context but no explicit exclusions.

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