Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

salvar_campo

Create or update a custom field in Ploomes CRM. Provide an existing key to update a field; omit it to create a new one.

Instructions

    Criar ou atualizar um campo customizado no Ploomes CRM.

    Passe a chave (Key) para atualizar um campo existente.

    Observacoes:
        1. Use buscar_entidades_campos para obter o EntityId.
        2. Use buscar_tipos_campo para obter o TypeId.
        3. Use buscar_tabelas_opcoes para obter o OptionsTableId (para campos do tipo lista).
        4. O campo Key eh retornado ao criar o campo e deve ser usado para salvar valores em OtherProperties.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nomeYes
chaveNo
ordemNo
tipo_idYes
secao_idNo
entidade_idYes
obrigatorioNo
desabilitadoNo
tabela_opcoes_idNo
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions the operation is a write (create/update) and that Key is returned and used for OtherProperties. However, it fails to specify if updates are destructive, required permissions, rate limits, or side effects like overwriting existing data.

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, consisting of two clear paragraphs: a brief statement of purpose and numbered observations. It front-loads the main action. However, the observations could be integrated more seamlessly, and the structure is adequate but not exceptional.

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 the tool's complexity (9 parameters, no annotations, no output schema) and many sibling tools, the description is incomplete. It covers basic operation and prerequisites but lacks parameter definitions, behavioral details, and differentiation from similar tools like 'salvar_campo_formulario_pipeline'. An agent would struggle to use it correctly without external knowledge.

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 description coverage is 0%, so the description must compensate. It explains only three parameters (Key, EntityId, TypeId, OptionsTableId) but leaves out others like 'ordem', 'secao_id', 'obrigatorio', and 'desabilitado' without any explanation, making it incomplete for an agent to understand all inputs.

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 custom field in Ploomes CRM, with a specific verb and resource. It differentiates from sibling tools like 'excluir_campo' and 'buscar_campos' by focusing on creation/update, but could be more explicit about its scope relative to pipeline field tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides essential prerequisites by listing tools to obtain EntityId, TypeId, and OptionsTableId. It also explains when to use the Key for updates. However, it lacks guidance on when not to use this tool (e.g., for pipeline fields) and does not mention alternatives or context of use.

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