PlanfixMCP

Overview Schema Source Related Servers Discussions Admin

create_contact

Create a contact or company record in Planfix by providing details like name, email, phone numbers, address, and custom fields.

Instructions

Создать контакт или компанию

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_contact"
  }
}

Input Schema

Name	Required	Description
`id`	No	Contact/company number. For create requests this field is usually omitted.
`name`	No	First name of a contact or name of a company.
`site`	No	Website URL of the contact/company.
`email`	No	Primary email address of the contact or company.
`files`	No	Existing Planfix files attached to the contact/company. Each item must contain an existing file id.
`group`	No	Contact group. Specify an existing group by id.
`skype`	No	Skype username.
`gender`	No	Contact gender. Use Female, Male, or NotDefined.
`phones`	No	Contact phone numbers. Each phone contains a number and phone type.
`address`	No	Postal address of the contact/company.
`midname`	No	Middle name of the contact.
`viberId`	No	Viber identifier associated with the contact/company.
`contacts`	No	Contacts linked to this company. Specify existing contact/company numbers.
`facebook`	No	Facebook profile/page link.
`lastname`	No	Last name of the contact.
`position`	No	Job title or position of the contact.
`telegram`	No	Telegram username or profile link.
`template`	No	Contact/company template. Specify an existing contact template by number.
`timezone`	No	IANA Time Zone Database identifier (TZID).
`birthDate`	No	Contact birth date. May be provided as a TimePoint-like object with date or as a supported date string.
`companies`	No	Companies linked to this contact. Specify existing contact/company numbers.
`instagram`	No	Instagram profile link.
`isCompany`	No	Whether the record is a company rather than an individual contact.
`isDeleted`	No	Whether the contact/company is deleted.
`telegramId`	No	Telegram identifier associated with the contact/company.
`description`	No	Description or notes for the contact/company.
`supervisors`	No	Contact supervisors. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92.
`languageCode`	No	Planfix interface language code for the contact/company.
`sourceObjectId`	No	Unique identifier of the specific object in the third-party application or system.
`customFieldData`	No	Custom field values for the contact/company. Each item contains a custom field id in field.id and its value.
`sourceDataVersion`	No	Version of the object data in the third-party application or system.
`communicationLanguageCode`	No	Preferred communication language code.

Output Schema

Name	Required	Description	Default
`id`	Yes
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations present, the description carries the full burden of behavioral disclosure. It merely says 'Create contact or company' and does not mention permissions, validation rules, side effects, or response behavior. For a mutating operation, this is minimal transparency.

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?

The description is a single, short sentence with no filler or unnecessary words, making it easy to parse. It is not as rich as it could be, but from a conciseness perspective it is efficient and front-loaded with the action and resource.

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?

The rich input schema and presence of an output schema fill in many operational details, so the terse description is acceptable for a simple create operation. However, with 32 optional parameters and no annotations, the description still lacks high-level guidance on when to choose this tool over bulk import or how to structure a typical request, leaving clear gaps.

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?

The input schema provides complete descriptions for all 32 parameters (100% coverage), so the description does not need to repeat field meanings. However, the description adds no additional semantic value beyond what the schema already offers; it only implies the contact/company distinction, which is explicitly covered by the isCompany parameter.

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 ('Создать' / create) and the resource ('контакт или компанию' / contact or company). It is specific enough to indicate the tool's purpose, but it does not explicitly differentiate it from sibling tools like import_contacts or update_contact, so it falls short of a top score.

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?

No guidance is given on when to use this tool versus alternatives such as import_contacts for bulk creation or update_contact for modifying existing records. The description only names the action and provides no context about prerequisites, typical use cases, or exclusions.

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