Skip to main content
Glama
novacrm-mcp

novacrm-mcp

novacrm_get_product

Retrieve a specific product's details by ID to view product information from a NovaCRM store.

Instructions

Obtém os detalhes de um produto específico pelo ID.

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

Input Schema

NameRequiredDescriptionDefault
idYesID do produto

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. 'Obtém' implies a read, but it says nothing about behavior on an invalid/nonexistent ID, permissions, or what is returned (a full product object vs partial).

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, front-loaded sentence with no waste. It is appropriately sized for a one-parameter getter, though it could carry slightly more routing detail without bloat.

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 simple single-parameter lookup with a fully documented schema, the description is minimally adequate. Without an output schema, however, it doesn't describe what 'detalhes' includes, leaving the return shape unknown.

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%, with the only parameter 'id' documented as 'ID do produto'. The description adds nothing beyond the schema, 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?

The description states a specific verb and resource ('Obtém os detalhes de um produto específico pelo ID'), making the single-record fetch unambiguous. It does not explicitly contrast with siblings like novacrm_list_products, but the 'específico pelo ID' phrasing implies the distinction.

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 explicit guidance on when to use this instead of novacrm_list_products or what preconditions apply (e.g., product must exist). Usage is only inferable from 'pelo ID'.

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