Skip to main content
Glama
novacrm-mcp

novacrm-mcp

novacrm_list_automations

List a NovaCRM store's automation rules, including triggers and actions, and optionally include archived copies created by duplicate review.

Instructions

Lista as regras de automação da loja (gatilhos e ações). Use includeArchived para ver cópias arquivadas pela revisão de duplicatas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "novacrm_list_automations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItens por página (1–100, padrão 50)
offsetNoDeslocamento da paginação (padrão 0)
includeArchivedNoIncluir cópias arquivadas (padrão false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that archived duplicates exist as a byproduct of the duplicate-review process, but says nothing about permissions, read-only nature, result ordering, or how many rules are typically returned.

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

Conciseness5/5

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

Two short sentences with no filler; the core purpose comes first and the flag guidance follows. Every clause carries information.

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

Completeness4/5

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

For a read-only listing tool with three optional, fully documented params and no output schema, the description covers what is returned (triggers and actions) and the archival nuance. Only the relationship to novacrm_get_automation and pagination expectations are unaddressed.

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

Parameters3/5

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

Schema coverage is 100%, so limit, offset, and includeArchived are already documented with defaults and ranges. The description adds only a rationale for includeArchived (copies archived by duplicate review) and no extra detail on paging behavior, so the baseline of 3 applies.

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?

States a specific verb ('Lista') and resource ('regras de automação da loja'), and clarifies the content of those rules (gatilhos e ações). It is clearly distinct from novacrm_get_automation for a single rule, though it never explicitly contrasts itself with siblings.

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 second sentence gives guidance only for the includeArchived flag, not for when to choose this tool over novacrm_get_automation or how to page through results. Usage as a bulk listing tool is implied by the verb rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.