Skip to main content
Glama
LeadFlow MCP

LeadFlow MCP

by kfairy9999

Create lead

create_lead

Add a lead to the shop pipeline with contact, service, source, and optional value; reuse an idempotency key on retries to avoid duplicates and receive a rule-based priority score.

Instructions

Add a lead to the shop pipeline. Money is integer cents (480000 = $4,800.00), never dollars. Pass an idempotencyKey when retrying so a duplicate submit returns the original lead. A reused key with a different payload is a conflict. The response includes the rule-based priority score.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contactName": "<contactName>",
      "service": "<service>",
      "source": "<source>"
    },
    "name": "create_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
emailNoOptional. Use null when the caller did not give one.
notesNo
phoneNoOptional. Digits, spaces, and + ( ) . - only.
stageNoDefaults to new.
sourceYesHow the lead arrived.
serviceYesThe job in the customer’s words.
urgencyNoDefaults to normal.
contactNameYesPerson to call back. Not a company name.
idempotencyKeyNoSend the same key on retry to avoid a duplicate lead. A different payload with the same key is a conflict.
estimatedValueCentsNoInteger cents, not dollars. 480000 means $4,800.00. Use 0 when unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the generic write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description carries real weight and does so: it discloses duplicate-submit behavior, the reused-key conflict condition, and that the response carries a rule-based priority score. The idempotentHint=false annotation means the call is not automatically idempotent, which the description's opt-in idempotencyKey wording is consistent with, not contradictory.

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?

Four short sentences, front-loaded with the purpose, then the unit trap, then the idempotency rule, then the return value. No filler, and the highest-consequence detail (cents vs dollars) appears early.

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

Completeness4/5

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

For an 11-parameter mutation with no output schema, the description covers units, duplicate/conflict behavior, and the shape of the return at a level sufficient to call it correctly. It stops short of stating what identifier is returned or what happens to optional fields when omitted, which are minor given a mostly documented schema.

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 coverage is 82%, so the schema already documents parameters such as estimatedValueCents and idempotencyKey. The description reinforces the highest-risk trap (integer cents, 480000 = $4,800.00) and retry semantics, which is useful emphasis, but it adds no meaning absent from the schema and doesn't touch the remaining 18% of undocumented fields.

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?

States a specific verb and resource plus the domain ("Add a lead to the shop pipeline"), which clearly separates it from get_lead/update_lead by implication. It never names a sibling explicitly, so an agent must infer that 'add' means create-not-update, but the intent is unambiguous.

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?

Gives real guidance on the retry/idempotency path ("Pass an idempotencyKey when retrying") but offers no tool-selection guidance relative to siblings such as update_lead or score_lead, and no prerequisites or when-not-to-use cases. Usage is implied by the create verb rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.