Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

salvar_checklist_etapa_completo

Create or update stage checklists in Ploomes CRM with dynamic fields and filters for frontend compatibility.

Instructions

    Criar ou atualizar um checklist de etapa de forma compatível com o front do Ploomes CRM.

    Cada item aceita, por exemplo:
        {
          "label": "CNPJ",
          "field_name": "CNPJ",
          "entity_id": 2,
          "type_id": 2,
          "required": true,
          "operation_id": 2
        }

    Para campos de opções pré-cadastradas (type_id=7), envie também:
        {
          "options_table": "Tabela Tipo de Documento",
          "options": ["CPF", "RG", "CNH"]
        }

    Observacoes:
        1. A tool garante campos dinâmicos, FieldKey, FieldPathId e o filtro do checklist.
        2. Usa DealFilterId no body final para que o checklist abra corretamente no front.
        3. checklist_id é opcional e permite atualizar um checklist existente.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nomeYes
itensYes
etapa_idYes
checklist_idNo
Behavior3/5

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

With no annotations, the description must disclose all behavioral traits. It mentions automatic handling of dynamic fields, FieldKey, FieldPathId, and DealFilterId, and notes that checklist_id is optional for updates. However, it does not state whether the tool is destructive, the return value, or error handling, leaving gaps in transparency.

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

Conciseness5/5

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

The description is concise (about 9 lines) and well-structured: it starts with a clear purpose, then provides examples, and ends with numbered observations. Every sentence adds value, and there is no redundant information.

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?

Given the tool's complexity (4 parameters, no output schema), the description explains the core functionality and provides parameter examples. However, it omits the return value (e.g., the created/updated checklist ID) and does not address error handling or integration with sibling tools, leaving the agent with incomplete contextual information.

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 input schema has 0% description coverage, but the description adds significant meaning: it provides detailed examples for the 'itens' parameter (normal and options variants) and clarifies that 'checklist_id' is optional for updates. The other parameters ('nome', 'etapa_id') are not further explained, but the description compensates well for the most complex parameter.

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 it creates or updates a stage checklist compatible with the Ploomes CRM front-end, which is a specific verb-resource pair. However, it does not explicitly distinguish from the sibling tool 'salvar_checklist_etapa', leaving the agent to infer the difference based on the 'completo' suffix and additional features mentioned.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'salvar_checklist_etapa'. It does not specify prerequisites, context, or when not to use it, leaving the agent to rely solely on the tool name and implicit differences.

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