Skip to main content
Glama

Add a lead by hand

dosai_create_lead

Create a lead that did not come through the bot (a phone call, a walk-in): name and a phone or an email, with a summary. Nothing is sent to the person. lead_status takes only the built-in values listed in its field; the project's own funnel step is set afterwards with dosai_update_lead. Requires editor role.

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_create_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
notesNoInternal note for the team.
phoneNo
summaryNoWhat the person wants.
project_idYesFrom dosai_list_projects.
client_nameNo
lead_statusNoDefault qualified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses the permission requirement ('Requires editor role') and confirms no outreach is triggered. It also warns that lead_status only accepts built-in values and that funnel steps are a separate operation. It stops short of covering duplicate handling or what the call returns, which keeps it below a 5.

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 purpose and scoping, then contact requirements, then side effects, then the constraint and prerequisite. Each sentence carries distinct information with no restatement of the title or the schema.

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 a 7-parameter mutation with no output schema, the description covers authorization, side effects, and the follow-up operation needed to complete the workflow. It leaves the return value (presumably the new lead identifier) and duplicate-lead behavior unstated, which is a minor but real gap.

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?

Schema description coverage is 57%, and the description compensates by stating the practical contact requirement (a name plus a phone or an email) even though the schema only marks project_id required, and by constraining lead_status to the built-in enum values. Remaining gaps such as notes vs. summary distinction are left to the schema's own field descriptions.

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 gives a specific verb and resource ('Create a lead') and immediately scopes it to leads that did not come through the bot, with concrete examples (phone call, walk-in). This distinguishes it from conversation-derived lead creation and, alongside its pointer to dosai_update_lead, lets an agent place it in the lead workflow without opening a schema.

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

Usage Guidelines5/5

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

It states the triggering context explicitly (offline/manual lead sources), names the follow-up tool for setting the project's funnel step (dosai_update_lead), and rules out post-creation messaging ('Nothing is sent to the person'). The when-to-use condition and the hand-off to the alternative are both spelled out rather than implied.

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