Skip to main content
Glama
alexd73

PlanfixMCP

by alexd73

create_project

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

Instructions

Создать проект

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoProject name.
filesNoExisting Planfix files attached to the project. Each item must contain an existing file id.
groupNoProject group. Specify an existing group by id.
ownerNoProject owner. Specify an existing employee by number.
parentNoParent project. Specify an existing project by number.
statusNoProject status. Specify an existing project status by id.
endDateNoProject end date as TimePoint.
overdueNoWhether the project is marked as overdue.
auditorsNoProject auditors. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92.
templateNoProject template. Specify an existing project template by number.
assigneesNoProject assignees. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92.
isDeletedNoWhether the project is deleted.
startDateNoProject start date as TimePoint.
descriptionNoProject description.
counterpartyNoProject counterparty. Specify an existing contact/company by number.
participantsNoProject participants. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92.
clientManagersNoProject 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.
sourceObjectIdNoUnique identifier of the specific object in the third-party application or system.
customFieldDataNoCustom field values for the project. Each item contains a custom field id in field.id and its value.
hiddenForClientsNoWhether the project is hidden for clients.
isCloseToDeadlineNoWhether the project is close to its deadline.
sourceDataVersionNoVersion of the object data in the third-party application or system.
hiddenForEmployeesNoWhether the project is hidden for employees.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
resultYes
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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexd73/PlanfixMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server