Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

aplicar_campos_novos_html_llm

Substitute placeholders in HTML with real custom field keys, producing final HTML for proposal templates.

Instructions

    Substituir as tags <newfield .../> do HTML escrito pelo agente
    (Claude) diretamente na conversa pelas tags <field key="..."> reais,
    usando as Keys atribuídas por criar_campos_novos_llm.

    Não chama nenhuma API nem LLM — é só a reconciliação local, pelo
    mesmo motivo de aplicar_campos_no_html_ia (a criação de campo não
    devolve de volta a posição no HTML, então a gente casa por "index").

    Parâmetros:
        html: o HTML escrito pelo agente (com <newfield index="N" .../>
            nos pontos de campo customizado que ainda não existem no
            Ploomes).
        campos_criados: a lista retornada por criar_campos_novos_llm
            (cada item com index e key).

    Retorno:
        html_final: pronto para ir em corpo_html/cabecalho_html de
            salvar_modelo_proposta (ou no HTML de uma página já existente
            via montar_bloco_produtos_proposta/salvar_modelo_proposta com
            pagina_id).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlYes
campos_criadosYes
Behavior3/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 states it's local, non-API, non-LLM, and matches by index. It does not disclose error handling, side effects, or limitations beyond the index matching. Adequate but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively long and includes explanations in Portuguese. While informative, it could be more concise (e.g., the last line about 'pelo mesmo motivo' adds little value). It is front-loaded with the main action.

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 no output schema, the description specifies the return 'html_final' and its usage. It covers inputs, outputs, and the matching mechanism. It lacks details on error cases, but overall provides sufficient context for correct use.

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?

Schema coverage is 0%, so the description must compensate. It explains that 'html' is the agent-written HTML with <newfield> tags, and 'campos_criados' is the list from criar_campos_novos_llm with index and key. This adds practical context not present in the schema.

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 defines the tool's purpose: replacing <newfield> tags with <field key> tags using keys from another tool. It specifies the source of keys (criar_campos_novos_llm) and the action (reconciliation). However, it does not differentiate from the sibling tool 'aplicar_campos_no_html_ia' beyond mentioning the same reason.

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 implies usage after criar_campos_novos_llm and notes it is local reconciliation (no API/LLM). It lists parameters but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives like aplicar_campos_no_html_ia.

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