Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

salvar_campo_formulario_pipeline

Add or move a field in a pipeline deal form. Specify the field key, form ID, and optionally section and order to update the form layout.

Instructions

    Adicionar ou mover um campo no formulário de negócios de um pipeline.

    Se o campo (FieldKey) já existir no formulário, ele é movido para a
    seção/posição indicada em vez de ser duplicado.

    Passe o ID do campo para atualizar diretamente sem busca prévia.

    Observacoes:
        1. Use buscar_formulario_pipeline para obter o form_id, secao_id e IDs de campos.
        2. chave_campo (FieldKey) deve ser uma das chaves nativas de negócio:
           - deal_title: Título do negócio
           - deal_amount: Valor
           - deal_currency: Moeda
           - deal_contact: Empresa (contato principal)
           - deal_person: Pessoa de contato
           - deal_tags: Marcadores
           - deal_origin: Origem
           - deal_owner: Responsável
           - deal_start_date: Data de início
           - deal_collaborating_users: Usuários colaboradores
           - deal_products: Produtos
           Para campos customizados, use a chave retornada por buscar_campos_entidades.
        3. largura_total=True faz o campo ocupar a linha inteira do formulário.
        4. ordenacao define a posição dentro da seção (menor = mais acima).
        5. Se secao_id não for informado, o campo fica no topo do formulário (sem seção).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
form_idYes
secao_idNo
ordenacaoNo
chave_campoYes
largura_totalNo
Behavior4/5

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

With no annotations provided, the description bears full burden. It discloses key behavioral traits: moving vs. duplicating, direct update via ID, and effects of parameters like secao_id and largura_total. It could mention error conditions but is mostly transparent.

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 structured with bullet points and numbered notes, each sentence adding value. It is front-loaded with the main action. Slightly verbose but appropriately sized for the complexity.

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

Completeness4/5

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

Given 6 parameters, no output schema, and no annotations, the description covers prerequisites, parameter meanings, and behavioral nuances. It is complete enough for an agent to invoke correctly, though return value and error handling are not detailed.

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

Parameters4/5

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

The schema has 0% coverage, so description must compensate. It explains chave_campo with a list of valid keys, ordenacao and largura_total semantics, and secao_id fallback. id is clarified for direct update. This adds significant meaning beyond the schema.

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 'Adicionar ou mover um campo no formulário de negócios de um pipeline.' This is a specific verb (add or move) and resource (form field of a pipeline), distinguishing it from siblings like 'salvar_secao_formulario_pipeline' and 'excluir_campo_formulario_pipeline'.

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 notes on prerequisites (use buscar_formulario_pipeline to get IDs), explains behavior when the field already exists (moved instead of duplicated), and provides a list of valid FieldKeys. While it doesn't explicitly state when not to use it, the context is clear enough for appropriate selection.

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