Skip to main content
Glama
novacrm-mcp

novacrm-mcp

novacrm_inventory_alerts

List low-stock products below a specified threshold or default 5 units, helping identify inventory items that need replenishment.

Instructions

Lista produtos em estoque baixo (abaixo do limite informado ou de 5 unidades).

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_inventory_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
thresholdNoLimite de estoque considerado crítico (padrão 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose the default threshold of 5 units — real behavioral information. However, it says nothing about whether out-of-stock (zero) items are included, result ordering, or size limits, which matters for a list/alert tool.

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?

A single compact sentence with the core filtering rule front-loaded and zero filler. Nothing can be trimmed without losing information.

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?

For a one-optional-parameter read tool this is adequate — the agent knows what it returns conceptually (products with low stock). But without annotations or an output schema, the description should say more about what a caller receives (product fields, inclusion of zero-stock items).

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 description coverage is 100% and the single threshold parameter is documented in the schema, so the baseline is 3. The description restates the default value (5) already present in the schema, adding no new meaning about units or how equality at the boundary is treated.

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 description states a specific verb+resource pair ('Lista produtos em estoque baixo') that an agent can act on immediately, and it defines what 'low' means (below the threshold, defaulting to 5). It does not explicitly distinguish itself from the nearby novacrm_list_products or novacrm_adjust_stock siblings, so it stops short of a 5.

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 low-stock framing implies the use case (finding products that need restocking) but there is no explicit when-to-use or when-not-to-use guidance, and no reference to the alternative novacrm_list_products. An agent must infer the routing decision from context alone.

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