PlanfixMCP

by alexd73

Overview Schema Source Related Servers Discussions Admin

Python

Remote

create_project

Create a project in Planfix by setting its name, description, timeline, team members, and custom field values.

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_project"
  }
}

Input Schema

Name	Required	Description
`name`	No	Project name.
`files`	No	Existing Planfix files attached to the project. Each item must contain an existing file id.
`group`	No	Project group. Specify an existing group by id.
`owner`	No	Project owner. Specify an existing employee by number.
`parent`	No	Parent project. Specify an existing project by number.
`status`	No	Project status. Specify an existing project status by id.
`endDate`	No	Project end date as TimePoint.
`overdue`	No	Whether the project is marked as overdue.
`auditors`	No	Project auditors. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92.
`template`	No	Project template. Specify an existing project template by number.
`assignees`	No	Project assignees. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92.
`isDeleted`	No	Whether the project is deleted.
`startDate`	No	Project start date as TimePoint.
`description`	No	Project description.
`counterparty`	No	Project counterparty. Specify an existing contact/company by number.
`participants`	No	Project participants. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92.
`clientManagers`	No	Project client managers. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92.
`sourceObjectId`	No	Unique identifier of the specific object in the third-party application or system.
`customFieldData`	No	Custom field values for the project. Each item contains a custom field id in field.id and its value.
`hiddenForClients`	No	Whether the project is hidden for clients.
`isCloseToDeadline`	No	Whether the project is close to its deadline.
`sourceDataVersion`	No	Version of the object data in the third-party application or system.
`hiddenForEmployees`	No	Whether the project is hidden for employees.

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

D1.7/5.0

Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as required permissions, side effects, return values, or whether the operation is reversible. The description carries the full burden and completely fails to address it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but this is under-specification rather than effective conciseness. The single phrase merely repeats the tool name and does not contribute meaningful content; it fails to earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 23 parameters and an output schema, the description is essentially empty. It lacks any high-level context about the creation process, required fields (even though none are formally required), or expected outcomes. This is severely inadequate for a tool of this complexity.

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 adds no parameter information beyond what the schema already provides, but it doesn't need to because the schema is thorough. However, it also doesn't highlight any important parameters or usage patterns, so it stays at baseline.

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

Purpose2/5

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

The description 'Создать проект' is essentially a translation of the tool name 'create_project', providing no additional specificity or differentiation from sibling tools like update_project or project_by_id. It states the obvious action but does not clarify scope or unique behavior.

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

Usage Guidelines1/5

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

The description gives no indication of when to use this tool versus alternatives such as create_task or update_project. There is no mention of prerequisites, context, or exclusions.

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