Skip to main content
Glama
novacrm-mcp

novacrm-mcp

novacrm_adjust_stock

Adjust product inventory by applying a positive or negative quantity delta and record each entry or exit movement, with an optional reason and low-stock alert threshold.

Instructions

Ajusta o estoque de um produto com registro de movimentação (entrada/saída).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productId": "<productId>",
      "quantityDelta": "<quantityDelta>"
    },
    "name": "novacrm_adjust_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoMotivo do ajuste (ex: reposição, correção de inventário)
productIdYesID do produto
quantityDeltaYesVariação de estoque: positivo soma (entrada), negativo subtrai (saída). Nunca 0.
lowStockThresholdNoLimite para disparar alerta de estoque baixo (padrão 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that a movement record is created, which is useful, but says nothing about whether stock can go negative, whether the adjustment is reversible, what permissions are needed, or what the operation returns.

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?

A single tight sentence with the core action front-loaded. It wastes nothing, though it also delivers little beyond the minimum.

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?

The schema is fully self-documenting, so the agent can call it, but for an unannotated mutation tool with no output schema the description should explain the resulting state (new stock level?), negative-stock handling, and threshold alert behavior. Those gaps leave it merely adequate.

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%, so all four parameters (including quantityDelta sign semantics and lowStockThreshold default) are already documented. The description's 'entrada/saída' restates the schema's sign convention rather than adding new meaning, so baseline 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 (ajusta) and resource (estoque de um produto) plus the side effect of logging a movement (entrada/saída). This clearly differs from destructive siblings like delete_product, though it doesn't explicitly contrast with novacrm_update_product, which could also plausibly touch stock.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this instead of novacrm_update_product or novacrm_inventory_alerts, no prerequisites, and no exclusions. The agent must infer the usage context from the name alone.

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