Skip to main content
Glama
novacrm-mcp

novacrm-mcp

novacrm_get_opportunity

Fetches an opportunity by ID and returns its client, value, and sales stage to inspect deal details.

Instructions

Obtém uma oportunidade pelo ID, com cliente, valor e estágio.

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

Input Schema

NameRequiredDescriptionDefault
idYesID da oportunidade

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/5.0
Behavior3/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 is clearly a read operation and it discloses the main payload fields (cliente, valor, estágio), which is useful, but it says nothing about behavior for an invalid/unknown ID or whether the result is scoped to the authenticated store.

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 front-loaded sentence with the verb first and no filler. Every clause, including the returned-field list, adds information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description is nearly sufficient: it names the lookup key and summarizes the returned fields. Only error behavior and store scoping are missing, which are minor for this complexity.

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 a single required 'id' parameter already documented as "ID da oportunidade". The description's "pelo ID" merely restates the schema, adding no format or sourcing guidance, so the 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?

The description states a specific verb and resource ("Obtém uma oportunidade pelo ID") and even names the key fields returned (cliente, valor, estágio). It implicitly distinguishes itself from novacrm_list_opportunities by the singular/ID-based framing, but never explicitly contrasts with it or with novacrm_update_opportunity.

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?

Usage is only implied: an agent can infer you call this when you already hold an opportunity ID and need its details. There is no explicit 'use this instead of list_opportunities when searching' guidance, and no stated prerequisites or exclusions.

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