Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

buscar_tarefas

Search for tasks in Ploomes CRM using filters such as type, date range, contact, business, or user. Retrieve paginated results to find specific assignments.

Instructions

    🔍 Pré requisitos:
        1. Você deve chamar a tool buscar_contato antes para buscar o id do contato se for informado algum contato.
        2. Você deve chamar a tool buscar_usuario antes para buscar o id do usuário se for informado algum usuário ou dono/proprietário da tarefa.
        3. Você deve chamar a tool buscar_negocio antes para buscar o id do negócio se for informado algum negócio.
        4. Você deve chamar a tool buscar_marcadores antes para buscar o id do marcador se for informado algum marcador.
        5. Você deve chamar a tool buscar_segmentos antes para buscar o id do segmento se for informado algum segmento de cliente.

    🔍 Observações:
      1. O resultado da busca é limitado a itens por página. Você pode acessar a próxima página usando o parâmetro pagina.
      2. Passe o ID do usuário logado quando o pedido for uma consulta pessoal, por exemplo: "minhas reuniões", "minha agenda", "minhas tarefas".
      3. Quando o tipo pedido pelo usuário não for explicitamente um dos permitidos(SIMPLES, VISITA, TELEFONE, EMAIL, REUNIAO, CONFERENCIA, WHATSAPP), pergunte ao usuário o tipo.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
tipoNo
paginaNo
conteudoNo
data_fimNo
equipe_idNo
contato_idNo
finalizadoNo
localidadeNo
negocio_idNo
data_inicioNo
marcador_idNo
ordenar_porNo
usuarios_idsNo
sentido_ordenacaoNo
id_segmento_clienteNo
duracao_maxima_em_minutosNo
duracao_minima_em_minutosNo
Behavior3/5

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

The description mentions pagination and result limits, and notes when to pass the user ID. However, it does not explicitly state that the tool is read-only or disclose side effects. Without annotations, more behavioral context would be beneficial.

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 uses bullet points and emojis for structure, making it scannable, but the prerequisite list is lengthy and could be more concise. Some information is duplicated in observations.

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 tool's complexity (18 parameters, no output schema, no annotations), the description lacks parameter explanations and return value details. It covers prerequisites and pagination but is incomplete for fully autonomous use.

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

Parameters1/5

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

The input schema has 18 parameters with 0% description coverage. The description only hints at a few parameters (e.g., pagina, contato_id, usuario_id via prerequisites) but fails to explain most parameters like conteudo, data_fim, localidade, etc.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description implies the tool searches tasks but does not explicitly state its purpose. It focuses on prerequisites and observations, leaving the primary function inferred.

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 clear prerequisites (must call other tools to get IDs) and usage observations (pagination, personal queries, type disambiguation). This helps the agent know when and how to use the tool, though it does not mention when not to use it.

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