Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

salvar_produto

Create a new product or update an existing one in Ploomes CRM. Use the product ID to update, or omit it to create.

Instructions

    Criar ou atualizar um produto no Ploomes CRM.

    Passe o ID para atualizar um produto existente.

    Observacoes:
        1. Use buscar_grupos_produto para obter o GroupId.
        2. Use buscar_familias_produto para obter o FamilyId.
        3. Use buscar_moedas para obter o CurrencyId.
        4. campos_customizados deve seguir o formato: [{"FieldKey": "chave", "StringValue": "valor"}]
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nomeYes
codigoNo
grupo_idNo
moeda_idNo
descricaoNo
familia_idNo
chave_externaNo
unidade_medidaNo
valor_unitarioNo
campos_customizadosNo
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool creates or updates, implying mutation, but lacks details on side effects, authorization requirements, rate limits, or what happens on conflict. The format note for custom fields helps, but overall transparency is low.

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 fairly concise, with main purpose in the first sentence and bullet-pointed observations. It front-loads the essential info. Could be slightly more structured, but overall efficient.

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 11 parameters, no output schema, and no annotations, the description is incomplete. It lacks information on return value, error handling, pagination, or any post-invocation behavior. For a complex tool with many siblings, more context is needed.

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?

Schema coverage is 0%, meaning no parameter descriptions are in the schema. The description only explains the 'id' parameter (for update) and the 'campos_customizados' format. None of the other 9 parameters are explained, leaving the agent to guess their meanings.

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 the tool creates or updates a product in Ploomes CRM, using specific verbs and resource. It distinguishes from sibling tools like 'salvar_produto_contato' by focusing on product entity, but does not explicitly differentiate from 'buscar_produtos' or 'excluir_produto'.

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 provides clear usage guidance: pass ID for updates, and lists prerequisite tools for GroupId, FamilyId, and CurrencyId. It also specifies format for custom fields. However, it does not mention when not to use this tool or alternatives for other operations.

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