Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

salvar_campo_formulario_proposta

Add or move a simple field in a proposal form. Specify the field key, target section, and whether it should occupy full width.

Instructions

    Adicionar ou mover um campo simples no formulário de um modelo de
    Proposta/Venda/Documento.

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

    Observações:
        1. Use buscar_templates_documentos para obter o template_id, ou
           informe form_id diretamente.
        2. Use buscar_formulario_proposta para ver os campos já existentes,
           os IDs de seção e os FieldKeys nativos (ex.: quote_amount,
           quote_expiration_date) ou personalizados (via
           buscar_campos_entidades).
        3. largura_total=True faz o campo ocupar a linha inteira do
           formulário.
        4. Esta ferramenta só cria campos simples (um valor por campo).
           Blocos repetíveis (produtos/parcelas) NÃO são criados por uma API
           de campo de formulário — o Ploomes deriva o formulário a partir
           do parsing do HTML do modelo (BodySourceCode). Tentar forçar um
           bloco por aqui cria um campo com QuickFormId nulo (quebrado, sem
           efeito). Para o bloco de Produtos, use
           montar_bloco_produtos_proposta em vez desta ferramenta.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
form_idNo
secao_idNo
ordenacaoNo
chave_campoYes
template_idNo
largura_totalNo
Behavior4/5

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

With no annotations, the description covers key behaviors: it can add or move fields, only handles simple fields, and explains effects like full-width. It lacks mention of idempotency or authentication, but overall is 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 well-structured with bullet points and front-loaded purpose. While slightly lengthy, each sentence adds value and no waste.

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

Completeness5/5

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

Given the complexity (7 parameters, no output schema), the description fully covers prerequisites, behavior, limitations, and alternative tools. An agent can confidently use this tool.

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 description coverage is 0%. The description adds meaning for some parameters (form_id, template_id, largura_total, chave_campo) via examples and notes, but 'id' remains unexplained. Adequate but not comprehensive.

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 adds or moves a simple field in proposal/sale/document forms. It distinguishes itself from sibling 'montar_bloco_produtos_proposta' by explicitly noting that blocks are not handled. The verb and resource are specific.

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

Usage Guidelines5/5

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

Explicit guidance is given on when to use (simple fields) and when not to (product blocks). It provides step-by-step instructions to retrieve necessary IDs and mentions alternative tools for blocks.

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