Skip to main content
Glama
advenimus

SyncroMSP MCP Server

leads_create

Create a new lead. To later remove it, update with disabled=true as leads cannot be deleted.

Instructions

Create a new lead. Note: leads have no DELETE endpoint. To soft-delete, use leads_update with disabled=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
first_nameNoFirst name
last_nameNoLast name
business_nameNoBusiness name
emailNoEmail
phoneNoPhone
mobileNoMobile
addressNoAddress
cityNoCity
stateNoState
zipNoZIP
statusNoStatus
ticket_subjectNoTicket subject
ticket_descriptionNoTicket description
ticket_problem_typeNoProblem type
hidden_notesNoHidden notes
user_idNoAssigned user ID
customer_idNoExisting customer ID
contact_idNoContact ID
location_idNoLocation ID
opportunity_amount_dollarsNoOpportunity amount in dollars
likelihoodNoLikelihood (0-100)
opportunity_start_dateNoOpportunity start date
appointment_timeNoAppointment time
appointment_type_idNoAppointment type ID
propertiesNoCustom field values
ticket_propertiesNoTicket custom field values
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions the lack of a DELETE endpoint but does not disclose any other behavioral traits such as side effects, required permissions, return value, or error handling. This is insufficient for a create operation.

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 is two sentences: one stating the purpose and one adding a critical note about deletion. It is concise, front-loaded, and contains no unnecessary 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 required fields, no output schema, and a note about deletion, the description lacks essential behavioral details such as what happens on success, duplicate handling, or any constraints. It is incomplete for a complex creation tool.

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 all 26 parameters having individual descriptions. The tool description does not add any extra meaning beyond the schema, so the baseline score of 3 applies.

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 'Create a new lead,' which is a specific verb+resource combination. It distinguishes from siblings by noting the absence of a DELETE endpoint and suggesting leads_update for soft-delete, but does not explicitly differentiate from leads_get or leads_list.

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

Usage Guidelines3/5

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

The description provides a clear action (create) and a warning about deletion with an alternative (leads_update), which gives some usage context. However, it does not specify when to use this tool versus other sibling tools like leads_list or leads_get.

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