Skip to main content
Glama
sanjibani

singleops-mcp

by sanjibani

create_lead_with_new_client

Create a lead and a new client profile in one request. Pass first name, last name, and operation ID; optional details like email or phone help deduplication.

Instructions

Create a lead (Job) for a brand-new client, in a single call.

Use this when the prospect is NOT yet in SingleOps. The new client profile is created under the "portal_lead" object inside the same request — the lead is attached to that new client automatically.

At minimum pass first_name + last_name. Providing email or phone is strongly recommended so SingleOps can later deduplicate if the same person contacts you again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
tagsNo
emailNo
notesNo
phoneNo
mobileNo
addressNo
last_nameYes
first_nameYes
bill_addr_1No
bill_addr_2No
company_nameNo
operation_idYes
sales_rep_idNo
bill_addr_cityNo
visit_stage_idNo
bill_addr_stateNo
bill_addr_postal_codeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations exist, so the description bears full burden. It discloses key behaviors: creates client profile under 'portal_lead' and auto-attaches the lead, and mentions deduplication via email/phone. However, it omits side effects, auth requirements, rate limits, and error conditions, leaving significant transparency gaps.

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?

Six sentences conveying all critical information without redundancy. Key details are front-loaded: purpose, usage condition, minimal requirements, and a recommendation. Every sentence earns its place.

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?

Despite having an output schema, the description lacks coverage for the 18-input parameters and behavioral context (e.g., what happens on error, how operation_id is used). The sibling tool distinction is clear, but parameter and behavioral details are insufficient for an agent to use the tool correctly without guessing.

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

Parameters2/5

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

With 0% schema description coverage, the description should compensate but only explains first_name, last_name, email, and phone (and implies operation_id as required). The other 14 parameters (e.g., tags, notes, address fields) are completely unmentioned, failing to guide their usage.

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 the verb (create), resource (lead for new client), and differentiates from the sibling tool create_lead_for_existing_client by specifying 'when the prospect is NOT yet in SingleOps'. The context of a single call is also highlighted.

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

Usage Guidelines4/5

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

Explicitly advises to use when the client is new, recommends minimum fields (first_name, last_name), and suggests email/phone for deduplication. The sibling tool is implicitly referenced by the name create_lead_for_existing_client, but not mentioned directly in the description, which is a minor gap.

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/sanjibani/singleops-mcp'

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