Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

buscar_negocio

Search deals in Ploomes CRM by applying filters like client, pipeline, value, status, and date range. Returns deal data and total count.

Instructions

    🎯 Objetivo:
      1. Busca negócios (deals) no sistema Ploomes CRM e retorna os dados do negócio e o número de ocorrências conforme os filtros especificados.

    ℹ️ Informações úteis:
        - Formato para datas: YYYY-MM-DDTHH:MM:SS-03:00
        - Por padrão, os negócios são ordenados por data de última atualização. Para mostrar os negócios mais recentes ou mais antigos, ordene por CreateDate.

    📋 Prerequisitos:
      1. Faça o menor número de chamadas possíveis para obter os dados necessários.
      2. Se o usuário pedir para calcular o valor total das oportunidades, use 'calcular_valor_total = True', a informação será retornada no campo 'total_amount'.
      3. Usar buscar_contato para obter o id_cliente do cliente.
      4. Usar buscar_pipeline para obter o id_pipeline do pipeline.
      5. Usar buscar_pipeline para obter o id_etapa_pipeline do estágio do negócio dentro do pipeline.
      6. Usar buscar_razao_perda para obter o id_razao_perda da razão de perda do negócio.
      7. Usar buscar_marcadores para obter o id_marcador do marcador.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paginaNo
tituloNo
valor_fimNo
id_clienteNo
id_negocioNo
id_marcadorNo
id_pipelineNo
valor_inicioNo
bairro_clienteNo
cidade_clienteNoNome completo da cidade em letras maiúsculas e com acentos
estado_clienteNoNome completo do estado em letras maiúsculas e com acentos
id_razao_perdaNo
status_negocioNo
data_criacao_fimNo
dias_em_etapa_fimNo
id_etapa_pipelineNo
sentido_ordenacaoNodesc
tem_vendas_geradasNo
data_criacao_inicioNo
id_segmento_clienteNo
parametro_ordenacaoNoLastUpdateDate
calcular_valor_totalNo
dias_em_etapa_inicioNo
id_equipe_responsavelNo
tem_propostas_geradasNo
tem_tarefas_pendentesNo
id_usuario_responsavelNo
tem_interacao_registradaNo
data_ultima_interacao_fimNo
data_de_ganho_ou_perda_fimNo
data_ultima_interacao_inicioNo
data_de_ganho_ou_perda_inicioNo
buscar_negocios_dos_meus_clientesNo
Behavior3/5

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

No annotations are provided, so the description holds the full burden. It implies read-only behavior (returns data) but does not explicitly state non-destructive nature. It mentions default ordering by last update and date format, providing some behavioral context, but lacks details on side effects, rate limits, or data freshness. Adequate but not comprehensive.

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 verbose with emojis and multiple sections (goal, useful info, prerequisites). While it is structured, it could be more concise. Every sentence adds value, but the length is not excessive. Average conciseness.

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

Completeness2/5

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

With 33 parameters, no output schema, and no annotations, the description leaves many gaps. It does not explain the return structure, pagination behavior beyond a default page, or maximum results. For a search tool with many filters, more contextual completeness is needed.

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 only 6% (only cidade_cliente and estado_cliente have descriptions). The main description adds context for calcular_valor_total and date format, and mentions pagination with pagina default. However, most parameters remain unexplained. The description adds some value but does not fully compensate for the coverage gap.

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's purpose: 'Busca negócios (deals) no sistema Ploomes CRM e retorna os dados do negócio e o número de ocorrências conforme os filtros especificados.' This distinguishes it from siblings like salvar_negocio (create) and excluir_negocio (delete). The verb 'buscar' (search) and resource 'negócio' are explicit.

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 provides concrete prerequisites, telling the agent to use other tools (buscar_contato, buscar_pipeline, etc.) to obtain necessary IDs and to minimize calls. However, it does not explicitly state when not to use this tool or when alternatives are better, but the context is sufficient.

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