Moxie CRM MCP Server

create_opportunity

Create a new sales opportunity in the pipeline, specifying stage, value, client, and expected close date to track potential deals.

Instructions

Create a new sales opportunity in the pipeline. Note: This endpoint (/action/opportunities/create) may not be officially documented. The official way to create opportunities is via form submissions with a pipelineStageName using create_form_submission.

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

Input Schema

Name	Required	Description
`name`	Yes	Name/title of the opportunity
`stage`	No	Pipeline stage (use list_pipeline_stages to see available stages)
`value`	No	Estimated value of the opportunity
`clientName`	No	Client associated with this opportunity
`contactName`	No	Contact person for this opportunity
`description`	No	Description of the opportunity
`probability`	No	Win probability percentage (0-100)
`expectedCloseDate`	No	Expected close date (YYYY-MM-DD format)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Aug 2, 2026

TDQS

A4.2/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 transparency burden. It discloses a notable behavioral trait: 'This endpoint (/action/opportunities/create) may not be officially documented,' alerting the user to potential instability or lack of support. However, it does not mention side effects, permissions, or return values, which are important for a mutation tool. The unofficial-status disclosure adds value but is not comprehensive.

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 only two sentences, both of which are necessary. The first sentence delivers the core purpose, and the second provides a critical caveat and alternative. There is no redundant or filler content, so it is appropriately sized and front-loaded.

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?

Despite having 8 parameters and no output schema, the description provides a clear purpose and an essential alternative recommendation. It could be more complete by mentioning what the endpoint returns or prerequisites like authentication, but the caveat about its unofficial status is crucial for decision-making. Given the schema covers parameter semantics, the description is mostly sufficient for correct usage.

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 baseline is 3. The description does not add any parameter-level meaning beyond what the schema already provides. The note about pipelineStageName refers to the sibling tool, not this one, so it does not clarify parameters here. The schema descriptions themselves are adequate for all 8 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Create a new sales opportunity in the pipeline.' The verb 'create' and resource 'sales opportunity' are specific, and the note distinguishing this from the official create_form_submission method differentiates it from a key sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides an alternative and a when-not-to-use signal: 'The official way to create opportunities is via form submissions with a pipelineStageName using create_form_submission.' This tells the agent to prefer the sibling tool, which is clear usage guidance. It implies that this endpoint should be used only if the official method is unavailable or inappropriate.

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