Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

montar_modelo_proposta_com_identidade

Automates proposal model creation with visual identity: generates HTML, form sections, fields, and product block in one call.

Instructions

    Atalho de ponta a ponta para "CPQ com identidade visual": gera o HTML
    (mesma lógica de gerar_identidade_visual_proposta), cria o modelo
    (mesmo payload de salvar_modelo_proposta), cria as seções/campos
    simples do formulário e, se incluir_bloco_produtos=True, monta o
    bloco de produtos (mesma lógica de montar_bloco_produtos_proposta) —
    tudo numa única chamada.

    Pré-requisito: os parâmetros visuais (cor_primaria/cor_secundaria/
    logo_url/fonte) e a lista de secoes/campos devem vir de um brief JÁ
    EXTRAÍDO pelo agente a partir dos arquivos de referência anexados
    pelo usuário (manual de marca, logotipo, propostas/pedidos atuais,
    exemplos de produtos, processos, planilha de campos). Esta tool não
    lê arquivos — quem lê é o agente, com os próprios tools de
    leitura/skill de PDF, ANTES de chamar esta tool.

    Use as tools individuais (gerar_identidade_visual_proposta,
    salvar_modelo_proposta, salvar_secao_formulario_proposta,
    salvar_campo_formulario_proposta, montar_bloco_produtos_proposta) em
    vez desta se precisar de controle fino sobre cada etapa, ou se algo
    falhar no meio do caminho e for preciso retomar de onde parou.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fonteNoArial, Helvetica, sans-serif
secoesNo
logo_urlNo
entidade_idYes
nome_modeloYes
cor_primariaYes
nome_empresaYes
rodape_textoNo
cor_secundariaNo
campos_bloco_produtosNo
incluir_bloco_produtosNo
Behavior4/5

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

No annotations provided, but description discloses that this tool does not read files (agent must prepare data), it combines multiple steps, and the product block inclusion is conditional. However, it does not mention potential failure modes or side effects beyond mentioning individual tools for recovery.

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?

Well-structured with clear sections: overview, prerequisites, alternatives. The description is informative without being verbose. Could condense slightly, but overall effective.

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

Completeness3/5

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

For a tool with 11 parameters, no output schema, and complex composition, the description provides adequate context about the purpose and flow but lacks detailed parameter constraints or return value expectations.

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%, so description must compensate. It adds meaning by grouping visual parameters (cor_primaria, cor_secundaria, logo_url, fonte) and explaining secoes, incluir_bloco_produtos, and campos_bloco_produtos. However, not all 11 parameters are explained (e.g., nome_modelo, entidade_id, nome_empresa, rodape_texto). Partial compensation.

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 it is a shortcut for 'CPQ com identidade visual' that generates HTML, creates model, sections/fields, and optionally builds product block. It distinguishes itself from sibling tools by explicitly naming them and clarifying it combines their logic in a single call.

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?

Provides explicit when-to-use and when-not-to-use guidance: use individual tools for fine control or recovery after failure. Also states prerequisites: visual parameters and sections must come from a brief already extracted by the agent via other tools.

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