Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

buscar_proposta

Search proposals in Ploomes CRM using filters like client, value, date, pipeline, and approval status. Order results by fields such as creation date or value.

Instructions

    🔍 Observações:
      - Caso não especificado, ordernar por CreateDate desc para mostrar propostas mais recentes.
      - Caso peçam para filtrar a busca por equipe, use a tool buscar_equipes_de_usuarios para buscar o id da equipe, quando necessário, peça para que o usuário especifique o nome da equipe.
      - O campo descricao_entrega é um campo de texto descrevendo a previsão de entrega da proposta, como 'semana que vem', '10 dias', '2 semanas', etc.
      - O campo Approver é um campo booleano que indica se a proposta está aguardando aprovação do usuário logado.
      - Uma proposta é identificada pelos campos QuoteNumber e Id. Cada proposta pode ter várias revisões, o número da revisão é indicado pelo campo ReviewNumber (numero_da_revisao). O campo Id é diferente para cada revisão, enquanto o campo QuoteNumber é o mesmo para todas as revisões de uma mesma proposta.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeloNo
paginaNo
tituloNo
valor_fimNo
id_clienteNo
id_produtoNo
id_pipelineNo
id_propostaNo
ordenar_porNo
valor_inicioNo
buscar_revisoesNo
desconto_maximoNo
desconto_minimoNo
data_criacao_fimNo
metodo_pagamentoNo
descricao_entregaNo
id_etapa_pipelineNo
numero_da_revisaoNo
sentido_ordenacaoNo
localidade_clienteNo
numero_da_propostaNo
data_criacao_inicioNo
data_vencimento_fimNo
id_segmento_clienteNo
id_equipe_responsavelNo
data_vencimento_inicioNo
id_usuario_responsavelNo
buscar_minhas_propostasNo
data_compartilhamento_fimNo
aguardando_minha_aprovacaoNo
proposta_aceita_por_clienteNo
data_compartilhamento_inicioNo
data_ultima_visualizacao_fimNo
data_ultima_visualizacao_inicioNo
status_aprovacao_usuario_internoNo
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses default ordering behavior and revision handling. However, it does not mention permissions, rate limits, pagination behavior, error handling, or whether query is read-only. Adds some context but incomplete.

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?

Description is structured as bullet points, making it moderately easy to scan. However, it is verbose and includes redundant details. Could be more concise by grouping related information.

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 complexity (35 parameters, no output schema, no annotations), the description is incomplete. It explains revision details but does not cover pagination, output format, or how to combine multiple filters. Leaves significant gaps for an agent to use effectively.

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 has 35 parameters with 0% description coverage. Description explains a few parameters (descricao_entrega, Approver, sorting fields, revision fields) but many remain unexplained (e.g., localidade_cliente, metodo_pagamento, etc.). Fails to compensate adequately for lack of schema descriptions.

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 name 'buscar_proposta' clearly indicates search for proposals. Description explains sorting default and revision identification, distinguishing from tools like 'salvar_proposta' or 'excluir_proposta'. However, it doesn't explicitly differentiate from other 'buscar_*' tools like 'buscar_clientes'.

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?

Description provides usage context: default ordering, when to use 'buscar_equipes_de_usuarios' for team filtering, and explains fields like 'descricao_entrega' and 'Approver'. It gives explicit guidance on prerequisites for team filtering.

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