Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

buscar_clientes

Search for clients (companies or contacts) by name, document, location, or status. Retrieve contacts linked to a specific company using its parent company ID.

Instructions

    šŸŽÆ Objetivo:
        1. Busca clientes (empresas ou contatos).
        2. Busca contatos de empresa (por exemplo: João da Sunhub).

    šŸ” InstruƧƵes para buscar os contatos de uma empresa:
        1. Primeiro chame a tool buscar_clientes para buscar o ID da empresa.
        2. Depois chame a tool buscar_clientes novamente para buscar os clientes relacionados ao ID da empresa pai.

    šŸ” ObservaƧƵes:
        1. Só use o campo STATUS quando o pedido explicitar qual o status.
        2. Use o campo id_da_empresa_pai quando quiser buscar por contatos de alguma empresa, por exemplo: João da GlobalTech.
        3. NÃO tente preencher o tipo a partir do contexto da frase ou de situações genéricas (como 'clientes da região XXXXX'). O campo "tipo" deve ser preenchido em duas situações:
            - Se o usuƔrio indicar explicitamente o tipo.
            - Se o nome do cliente for mencionado (tente prever pelo nome como por exemplo, 'JoĆ£o' → PESSOA, 'Microsoft' → EMPRESA).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
cpfNo
cnpjNo
nomeNo
tipoNoNAO_IDENTIFICADO
bairroNo
cidadeNo
paginaNo
statusNo
cargo_idNo
estado_ufNoNome completo do estado em letras maiĆŗsculas e com acentos
marcador_idNo
ordenar_porNo
segmento_idNo
possui_vendasNo
id_da_empresa_paiNo
sentido_ordenacaoNo
data_cadastro_antes_deNo
usuario_responsavel_idNo
data_cadastro_depois_deNo
data_ultima_venda_antes_deNo
data_ultima_venda_depois_deNo
data_ultimo_negocio_antes_deNo
data_ultimo_negocio_depois_deNo
data_ultima_interacao_antes_deNo
data_ultima_interacao_depois_deNo
possui_tarefas_pendentes_ou_em_abertoNo
Behavior2/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 does not disclose whether the tool is read-only, requires authentication, has rate limits, or any side effects. It omits pagination behavior and return format, leaving significant gaps in behavioral context.

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

Conciseness2/5

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

The description is verbose with redundant instructions, an objective section, and detailed observations. It could be trimmed to a few crisp sentences. The structure is not front-loaded enough for quick parsing.

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 27 parameters, no output schema, and no annotations, the description should cover output format, pagination, defaults, and error states. It lacks these, making it incomplete for an agent to fully understand the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only 4% of parameters have descriptions in the schema (estado_uf). The description adds meaning for a few parameters (status, tipo, id_da_empresa_pai, id) but does not explain the many date filters, booleans, or other fields. Given the large schema, this insufficiently compensates for low coverage.

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 the tool searches for clients (companies or contacts) and can also search for contacts of a company. It specifies the verb and resource, but the procedural instructions muddy the clarity slightly, earning a 4 instead of 5.

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 explicit instructions on when to use certain parameters (e.g., status only when explicit, id_da_empresa_pai for company contacts) and outlines a two-step process for finding contacts of a company. However, it does not differentiate from other search tools or provide alternatives, capping the score at 4.

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