Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

by JoseAlmeida-Ploomes
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

buscar_gatilhos_acoes_automacao

Retrieve triggers and action types available for automations in Ploomes CRM. Use the returned IDs to configure automation rules.

Instructions

    Buscar os gatilhos (TriggerId) e tipos de ação (ActionId) disponíveis
    para automações no Ploomes CRM.

    Observações:
        1. Use o TriggerId retornado no parâmetro gatilho_id de salvar_automacao.
        2. Use o ActionId retornado dentro de cada ação da lista `acoes` de
           salvar_automacao.
        3. RestrictedEntityId (quando presente num gatilho) indica que aquele
           gatilho só é válido para uma entidade específica (ex.: gatilhos de
           "ganho"/"perda" só valem para Negócios).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paginaNo

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It implies read-only operation ('buscar'), but does not explicitly state safety, idempotency, or authentication requirements. Adequate but not thorough.

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

Conciseness4/5

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

Description is concise, with main purpose upfront and bullet-pointed observations. No fluff, but could benefit from structured sections.

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

Completeness3/5

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

Given the tool's simplicity (1 param, no output schema), explanation of trigger/action IDs and RestrictedEntityId is good. However, missing parameter description and output format details reduce completeness.

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 one parameter 'pagina' (integer, default 1) with 0% schema description coverage. The tool description does not explain this parameter, leaving users unaware of pagination behavior.

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?

Description clearly states it fetches available triggers (TriggerId) and action types (ActionId) for automations in Ploomes CRM. It specifies the returned elements and distinguishes from sibling tools like 'buscar_automacoes' which list automations themselves.

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?

Provides clear usage tips: how to use the returned TriggerId and ActionId with 'salvar_automacao', and explains the meaning of RestrictedEntityId. Lacks explicit when-not-to-use instructions, but sufficient for a lookup tool.

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