mcp-vtenext

create_opportunita

Create new sales opportunities in VTENext CRM by specifying name, status, estimated value, closing date, and description to track potential deals.

Instructions

Crea una nuova opportunità in VTENext

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": {
      "nome": "<nome>"
    },
    "name": "create_opportunita"
  }
}

Input Schema

Name	Required	Description	Default
`nome`	Yes	Nome dell'opportunità
`stato`	No	Stato (es. Prospecting, Qualification, Closed Won)	Prospecting
`importo`	No	Valore stimato
`data_chiusura`	No	Data chiusura prevista (YYYY-MM-DD)
`descrizione`	No	Note o descrizione

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 22, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Crea' implies a write/mutation operation, the description doesn't mention permission requirements, whether this operation is idempotent, what happens on success/failure, or any rate limits. For a creation tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a creation tool and gets straight to the point without unnecessary elaboration.

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 creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns an ID, confirmation message), error conditions, or system constraints. The combination of mutation operation + zero annotations + no output schema requires more comprehensive description than provided.

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 all 5 parameters thoroughly. The description adds no parameter information beyond what's in the schema. The baseline score of 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 ('Crea una nuova opportunità') and the target system ('in VTENext'), which is a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'update_opportunita' or explain what distinguishes creating from other opportunity-related operations.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_opportunita' or 'get_opportunita'. There's no mention of prerequisites, when this operation is appropriate, or what distinguishes it from other opportunity-related tools in the sibling list.

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

Deploy Server