Skip to main content
Glama
advenimus

SyncroMSP MCP Server

customers_create

Create a customer in SyncroMSP with business name, contact details, address, communication preferences, and custom fields. Phone and mobile auto-create entries.

Instructions

Create a new customer. Note: phone and mobile fields auto-create entries in the phones sub-resource.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
business_nameNoBusiness name
firstnameNoFirst name
lastnameNoLast name
emailNoEmail address
phoneNoPhone number
mobileNoMobile number
addressNoStreet address
address_2NoAddress line 2
cityNoCity
stateNoState
zipNoZIP code
notesNoNotes
get_smsNoReceive SMS notifications
opt_outNoOpt out of communications
no_emailNoNo email communications
get_billingNoReceive billing emails
get_marketingNoReceive marketing emails
get_reportsNoReceive report emails
ref_customer_idNoReferring customer ID
referred_byNoReferral source
tax_rate_idNoTax rate ID
notification_emailNoNotification email
invoice_cc_emailsNoInvoice CC emails
invoice_term_idNoInvoice term ID
propertiesNoCustom field values
consentNoConsent settings
Behavior4/5

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

The description explicitly discloses that phone and mobile fields auto-create entries in the phones sub-resource, which is a significant behavioral side-effect not captured by annotations (none provided). This adds transparency beyond the input schema. However, it does not mention other potential behaviors such as whether the created customer is returned, required permissions, or idempotency.

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

Conciseness5/5

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

The description consists of two concise sentences with no superfluous information. The first sentence states the core purpose, and the second provides a critical behavioral note. It is well-structured and front-loaded with essential information.

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

Completeness2/5

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

Given the tool has 26 parameters, no output schema, and no annotations, the description is too minimal. It fails to explain what the tool returns, error conditions, or prerequisites. While the phone note helps, the description is incomplete for an agent to reliably use the tool without additional context.

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

Parameters4/5

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

The input schema has 100% description coverage, so baseline is 3. The description adds value by noting the side-effect of phone and mobile parameters, which clarifies their behavior beyond the schema descriptions. This enhances understanding of the parameter semantics, justifying a score above baseline.

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

Purpose5/5

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

The description clearly states 'Create a new customer' with a specific verb and resource. The additional note about phone/mobile auto-creating entries in the phones sub-resource helps distinguish this tool from the sibling tool customers_create_phone, which is used to explicitly create phone entries for existing customers.

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. It does not mention that customers_create_phone should be used for adding phones to existing customers, nor does it specify any prerequisites or context (e.g., required fields or conditions for creation). The auto-create note implies a side-effect but not usage boundaries.

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/advenimus/syncromsp-mcp'

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