Skip to main content
Glama
alexd73

PlanfixMCP

by alexd73

update_project

Update an existing Planfix project by its number to modify details like name, status, timeline, and team assignments.

Instructions

Обновить проект по номеру

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumber of project
nameNoProject name.
groupNoProject group. Specify an existing group by id.
ownerNoProject owner. Specify an existing employee by number.
parentNoParent project. Specify an existing project by number.
silentNoSilent mode
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.
hasEndDateNoWhether the project has an end date.
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
failuresNo
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'update project by number' with no details on side effects, silent mode behavior, or whether fields are appended or replaced. This is insufficient for a mutation tool.

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 (three words), which is under-specification rather than conciseness. It does not front-load key usage details nor explain what happens on update, making it less helpful than a slightly longer but informative description.

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?

With 24 parameters, no annotations, and an output schema, the description 'Обновить проект по номеру' is completely inadequate. It gives no indication of update semantics, optionality, or expected behavior, leaving the agent without critical context.

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%, with each parameter having a description. The tool description adds no parameter-specific value, but the schema comprehensively documents each field, so baseline 3 is appropriate.

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 'Обновить проект по номеру' translates to 'Update project by number', clearly stating the verb and resource. It distinguishes from siblings by resource type, but lacks explicit scope or additional differentiator beyond the tool name itself.

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?

The description provides no guidance on when to use this tool versus alternatives like create_project or update_task. No context about prerequisites, permissions, or whether it supports partial updates.

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