Skip to main content
Glama
alexd73

PlanfixMCP

by alexd73

import_contacts

Import contact lists into Planfix with full details: names, phones, emails, companies, groups, and custom fields. Choose how to handle duplicates.

Instructions

Импортировать список контактов

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
silentNoSilent mode
contactsNo
sourceIdNoUnique identifier of the third-party application or system.
companyTemplateIdNo
contactTemplateIdNo
optionImportDuplicateNoEnum: ignore, update, none
optionImportUniqueFieldNoEnum: email-phone-name-ifnot, email-phone-name, email-phone, phone, name, email-and-phone-and-name, number, custom OR custom:{fieldId}
optionImportUniqueDefaultFieldNoEnum: name, email-phone-name
Behavior1/5

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

With no annotations, the description must carry the full burden, but 'Importar lista de contactos' reveals nothing about duplicate handling, templates, side effects, or whether it updates existing records. This is a significant gap 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 a single sentence with no wasted words, but it is severely under-specified for a tool with 8 parameters and a complex nested schema. Conciseness is achieved at the expense of usefulness.

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?

This is a complex tool (8 parameters, nested objects, many options) with no output schema and no annotations. The description provides no details on return values, duplicate import behavior, template usage, or other critical context needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description contains zero parameter information. With only 63% schema description coverage, the tool description should compensate for ambiguous parameters like optionImportDuplicate and optionImportUniqueField, but it does not.

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 ('import') and resource ('contacts'), so the basic purpose is evident. However, it does not distinguish from sibling tools like create_contact or update_contact, missing the 'list' aspect as a potential differentiator.

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?

There is no guidance on when to use this tool versus create_contact/update_contact, no exclusions, and no mention of batch vs. single insert. The description does not help the AI decide between alternatives.

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