Skip to main content
Glama
novacrm-mcp

novacrm-mcp

novacrm_move_opportunity

Move internship opportunities through sales funnel stages (lead, contact, proposal, negotiation, won/lost); won sets probability to 100, lost zeroes it and records a loss reason.

Instructions

Move uma oportunidade de estágio no funil (lead → contact → proposal → negotiation → won/lost). Ganho ajusta a probabilidade para 100; perdido zera e aceita motivo da perda.

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>",
      "stage": "<stage>"
    },
    "name": "novacrm_move_opportunity"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID da oportunidade
stageYesEstágio de destino
lossReasonNoMotivo da perda (quando stage=lost)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose real side effects: won sets probability to 100, lost zeroes it and consumes a loss reason. It does not say whether transitions are validated or reversible, whether stages can be skipped or moved backwards, or what permissions are needed.

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?

Two dense sentences with no filler, and the core action plus stage ladder is front-loaded before the won/lost side effects. Nothing is wasted, though the loss-reason clause could be folded in more tightly.

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 3-parameter mutation tool with no annotations and no output schema, the description covers the stage side effects well but omits error conditions, transition rules, and what the call returns. It is adequate to invoke correctly, but not complete for a write operation with zero annotation coverage.

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 the schema already documents id, stage (with enum), and lossReason, making 3 the baseline. The description adds some meaning by presenting the stages as an ordered funnel and clarifying that lossReason is only meaningful when stage=lost, but it adds no format or constraint detail beyond that.

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 ('Move') and resource ('oportunidade de estágio no funil') and enumerates the full stage ladder (lead → contact → proposal → negotiation → won/lost), so the operation is unambiguous. It does not distinguish itself from the sibling novacrm_update_opportunity, which plausibly could also change stage, leaving that boundary implicit.

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 tool versus novacrm_update_opportunity, and no prerequisites or exclusions. The only guidance is implicit in the funnel-stage framing; the second sentence describes side effects, not usage conditions.

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