Skip to main content
Glama

Send an enquiry to the team

create_lead

Sends the customer’s enquiry or call-back request, with their name and phone, to the business’s team, who contact them on WhatsApp or by phone. For when the customer has asked to be contacted. Only for businesses that take requests through AI assistants; others answer with their WhatsApp and chat links.

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": {
      "business": "<business>",
      "phone": "<phone>",
      "message": "<message>"
    },
    "name": "create_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailNo
phoneYesThe customer’s phone or WhatsApp number with country code, e.g. +91 98765 43210, shared by the customer to be contacted.
messageYesWhat the customer wants, in a sentence or two.
businessYesThe business id from find_businesses, e.g. "carat-story".
call_backNoThe customer asked to be called.
product_idNo
product_titleNo

Output Schema

NameRequiredDescriptionDefault
idNo
statusYes
next_stepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world write, so the safety profile is covered. The description usefully adds the downstream consequence that the business team contacts the customer via WhatsApp or phone, which explains why the phone parameter is required. It does not address duplicate submissions (relevant given idempotentHint=false), failure behavior, or what a successful submission returns.

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

Conciseness4/5

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

Two sentences, front-loaded with the core action and followed by the trigger and eligibility caveat. The trailing clause about businesses answering with WhatsApp and chat links is slightly indirect but earns its place by preventing misfires. No filler.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and annotations carry the mutation profile. Still, for an 8-parameter write tool the description leaves three optional parameters (email, product_id, product_title) with no explanation of when or why to supply them, which is a real gap for correct invocation.

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 50%, so the baseline is 3. The description maps to several parameters in prose (name, phone, message as 'enquiry', call_back as 'call-back request', business), but leaves email, product_id, and product_title completely unexplained, and adds no format or constraint detail beyond the schema.

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 opens with a specific verb and resource: it 'Sends the customer's enquiry or call-back request, with their name and phone, to the business's team.' That is concrete and distinguishable from a generic 'contact' action. It stops short of differentiating itself from plausible siblings like hand_off_to_team or request_visit, so it does not reach the top tier.

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?

It gives an explicit trigger ('For when the customer has asked to be contacted') and an eligibility constraint ('Only for businesses that take requests through AI assistants; others answer with their WhatsApp and chat links'). What is missing is guidance relative to alternative tools for the same intent (e.g. requesting a visit vs. a callback), so the agent must infer that choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources