Skip to main content
Glama
Sign In
@vitrion/zentria-mcp

@vitrion/zentria-mcp

Official
by vitrionbv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create-deal

Creates a sales deal in a specified pipeline with required title and pipeline ID, and optional stage, value, owner, person, organization, expected close date, and lost reason.

Instructions

Create a sales deal (POST /api/public/sales/deals). pipelineId is required. Scope: sales:write.

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": {
      "title": "<title>",
      "pipelineId": "<pipelineId>"
    },
    "name": "create-deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesDeal title.
valueNoDeal value.
stageIdNo
personIdNo
lostReasonNo
pipelineIdYesPipeline id.
ownerUserIdNo
organizationIdNo
expectedCloseDateNoISO date YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/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. It does disclose the HTTP method (POST) and the required auth scope (sales:write), but it says nothing about side effects, failure modes, validation behavior, or what happens with unmentioned optional fields.

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, dense sentence that front-loads the core action, includes the endpoint, flags a required parameter, and states the permission scope. Every element earns its place with zero filler.

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 tool with 9 parameters, no output schema, and no annotations, the description is too thin. It does not clarify field semantics (e.g., value units, currency), relationships between parameters, or what the API returns on success. More context is needed to call this reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 44%, so the description must compensate for undocumented parameters. It only restates that pipelineId is required (already in the schema) and adds no meaning for value, stageId, personId, lostReason, ownerUserId, organizationId, or expectedCloseDate.

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 states a specific verb and resource: 'Create a sales deal'. The HTTP endpoint is included for precision, and the name 'create-deal' clearly distinguishes it from update-deal, list-deals, and move-deal-stage among siblings.

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 implied by the name and resource pairing: this is the tool to create a deal, as opposed to update-deal or list-deals. However, there is no explicit guidance on when to prefer this over alternatives, prerequisites like existing pipelines or owners, or when not to use it.

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

Deploy Server

Other Tools