smart-npv-mcp

Create product

create_product

Create a product in the Smart NPV CRM by providing the product fields in the params object.

Instructions

Create a product. Fields go inside params. Note: this path (with capital-P 'Products') comes from the vendor docs but has not been verified against the live API yet — confirm with Smart NPV before relying on it.

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": {
      "params": "<params>"
    },
    "name": "create_product"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes	Object of fields passed to Smart NPV as documented in its API.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 1, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already indicate non-read-only, non-destructive, and open-world behavior. The description adds a relevant caution that the endpoint path is unverified and recommends confirmation with Smart NPV, which is useful behavioral context beyond annotations. However, it doesn't cover side effects, authorization, or error behavior.

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?

The description is short and front-loaded with the core action. The second sentence about fields is somewhat redundant, but the third sentence adds an important caveat. Overall, it is concise with minimal waste.

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?

For a create operation, the description lacks essential context: what fields are needed, what constitutes a valid product, expected response, or effects. It has no output schema, and the params object is open-ended. The note about vendor docs is helpful but doesn't complete the picture.

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?

The schema defines a single 'params' parameter described as 'Object of fields passed to Smart NPV as documented in its API,' which is vague. The description only says 'Fields go inside params,' adding no meaning. The internal structure of the params object is undocumented, so the description fails to compensate for the schema's lack of field-level detail.

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 clearly states the action 'Create a product' with a specific verb and resource. It distinguishes itself from sibling tools, as no other tool targets product creation. However, it doesn't elaborate on what a 'product' represents in this domain, leaving some ambiguity.

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?

No explicit guidance on when to use this tool versus alternatives, or when not to use it. The note about confirming with Smart NPV is a caution but not usage context. The description lacks prerequisites, use cases, or scenarios.

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