@vitrion/zentria-mcp

Official

Overview Schema Source Related Servers Discussions Admin

create-person

Create a sales person in Zentria CRM by providing name, email, phone, and organization ID. Adds new sales team members to your customer relationship management data.

Instructions

Create a sales person (POST /api/public/sales/people). 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": {
      "name": "<name>"
    },
    "name": "create-person"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Person name.
`email`	No	Email address.
`phone`	No	Phone number.
`organizationId`	No	Linked organization id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 8, 2026

TDQS

A4/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 behavioral disclosure burden. It does disclose the HTTP method (POST), the resource path, and the required auth scope ('sales:write'), which is useful. However, it does not mention response behavior, whether the operation is reversible, or what happens on duplicate names.

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, front-loaded sentence that states the action, the resource, the endpoint, and the required scope. Every element earns its place and there is no filler.

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 simple create operation with fully described input parameters, the description is largely complete: it identifies the resource, endpoint, and auth scope. The only notable gap is the absence of any return-value description, especially since no output schema is 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 all four parameters already have meaningful descriptions in the input schema. The tool description adds no param-level detail, but it does not need to because the schema is sufficient.

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 uses a specific verb ('Create') with a specific resource ('a sales person') and provides the exact POST endpoint. It is clearly distinct from sibling tools like update-person, get-person, and list-people.

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

Usage Guidelines4/5

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

The description clearly establishes that this tool is for creating a sales person, which differentiates it from read/update/delete siblings without explicitly naming alternatives. It does not provide when-not-to-use guidance, but the context is strong enough for an agent to select it correctly.

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

Deploy Server