Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

buscar_vendas

Search for active sales in Ploomes CRM and retrieve sale details along with count. Filter by owner, product, date range, amount, and more.

Instructions

    Objetivo:
      1. Busca vendas (orders) ativos no sistema Ploomes CRM e retorna os dados da venda e o número de ocorrências conforme os filtros especificados.

    Informações úteis:
        - Formato para datas: YYYY-MM-DDTHH:MM:SS-03:00
        - Caso não especificado, ordernar por CreateDate para mostrar as vendas mais recentes.
        - Quando for informado que determinado usuário vendeu algo, assuma que a venda é daquele usuário
        - Vendas de usuário são aquelas em o "id_dono" é o id do usuário.
        - Use o parâmetro "id_produto" para filtrar vendas que contenham um produto específico.
    Prerequisitos:
      1. Faça o menor número de chamadas possíveis para obter os dados necessários.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
chaveNo
paginaNo
id_donoNo
data_fimNo
id_moedaNo
id_vendaNo
descricaoNo
id_agenteNo
id_pessoaNo
valor_fimNo
id_clienteNo
id_criadorNo
id_produtoNo
data_inicioNo
id_pipelineNo
desconto_fimNo
eh_aprovadorNo
nome_estagioNo
tem_comissaoNo
valor_inicioNo
compartilhadoNo
numero_pedidoNo
id_atualizadorNo
desconto_inicioNo
data_criacao_fimNo
id_cotacao_origemNo
sentido_ordenacaoNodesc
id_nivel_aprovacaoNo
valor_comissao_fimNo
data_criacao_inicioNo
id_segmento_clienteNo
id_status_aprovacaoNo
parametro_ordenacaoNoCreateDate
comentarios_internosNo
equipe_responsavel_idNo
valor_comissao_inicioNo
data_ultima_atualizacao_fimNo
data_ultima_atualizacao_inicioNo
data_ultima_abertura_externa_fimNo
data_compartilhamento_externo_fimNo
data_ultima_abertura_externa_inicioNo
data_compartilhamento_externo_inicioNo
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions returning data and occurrence count, but does not clarify if the operation is read-only, authentication needs, rate limits, or side effects. The instruction to minimize calls is a behavioral hint but insufficient.

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 structured with bullet points and front-loaded with purpose. However, the 'Prerequisitos' section contains a guideline rather than a prerequisite, and some information could be more concise.

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?

Given the high complexity (43 parameters, no output schema, no annotations), the description is incomplete. It does not explain return format, pagination, or many filter parameters. It only covers basic usage hints.

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?

Schema description coverage is 0%, so the description must compensate. It only explains a few parameters indirectly (id_dono, id_produto, date format, ordering). With 43 parameters, the description provides minimal semantic help, leaving most parameters undefined.

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 vendas (orders) ativos' and returns data and occurrence count. It explicitly names the resource (vendas) and uses a specific verb (busca), distinguishing it from sibling tools that create, update, or delete.

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 provides some usage context, like date format and ordering hints, and a prerequisite to minimize calls. However, it does not differentiate this tool from other 'buscar' siblings (e.g., buscar_negocio, buscar_clientes) or specify when to use this over alternatives.

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