Skip to main content
Glama
novacrm-mcp

novacrm-mcp

novacrm_update_product

Update an existing product's details, price, or stock by sending only the fields you want to change; use the product ID to target the record.

Instructions

Atualiza dados, preço ou estoque de um produto existente (envie apenas os campos a alterar).

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": {
      "id": "<id>"
    },
    "name": "novacrm_update_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID do produto
nameNo
priceNo
stockNo
categoryNo
imageUrlNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.7/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. The partial-update contract ('send only the fields to change') is genuinely useful, but there is nothing on permissions, whether omitted fields are left intact, reversibility, or error behavior for an invalid id.

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?

One compact sentence with the mutation target and the partial-update rule front-loaded; nothing is wasted. It is slightly too terse for a 7-parameter mutation tool rather than padded.

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?

A mutation tool with no annotations, no output schema, and 6 undocumented parameters needs substantially more description than a single sentence, especially given the overlapping adjust_stock sibling.

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 description coverage is only 14% (just id), leaving 6 of 7 parameters undocumented. The description groups fields as 'dados, preço ou estoque', which hints at name/description/category/imageUrl vs price vs stock, but it does not compensate for the large coverage gap on category, imageUrl and description.

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 names a specific verb ('Atualiza') and resource ('um produto existente') plus the fields it can touch (dados, preço, estoque). It is clear what the tool does, but it does not distinguish itself from the sibling novacrm_adjust_stock, which overlaps on stock mutation.

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 statement of when to use this versus novacrm_adjust_stock for stock changes, nor versus novacrm_create_product/delete_product. The parenthetical 'envie apenas os campos a alterar' is invocation mechanics, not usage guidance.

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