Skip to main content
Glama

Update lead

dosai_update_lead
Destructive

Change a lead's status or contact details. The status must be one the project defines; an invalid value comes back with the valid list.

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>",
      "lead_id": "<lead_id>"
    },
    "name": "dosai_update_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
phoneNo
lead_idYes
project_idYesFrom dosai_list_projects.
client_nameNo
lead_statusNo

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. Changed2 schema fields changed
    • removedInput schema / properties / lead_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)$"
    • 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. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=false, so the safety profile is largely carried by structured data. The description adds genuinely useful behavior beyond that: an invalid status is rejected with the valid list returned, which is a real validation contract. It does not disclose whether omitted fields are preserved or cleared, which matters for a destructive-marked partial update.

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?

Two short sentences, front-loaded with the mutation surface and followed by the one non-obvious constraint about status values. Nothing is redundant and no sentence is padding.

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?

For a six-parameter mutation flagged destructiveHint=true with 17% schema coverage and no output schema, more is needed: whether the call is a partial update, whether sending fields can blank existing values, where the valid status list should be sourced, and what the update returns are all unstated. The definition covers the happy path but leaves the risky semantics to inference.

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 only 17% — just project_id ('From dosai_list_projects'), and zero parameters have enums despite lead_status being constrained by project configuration. The description does name the updatable surface ('status or contact details'), loosely covering lead_status, email, phone and client_name, and explains the validation path for an invalid status. It does not map field names, formats, or optional-field behavior, so it only partially compensates for the coverage gap.

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 uses a concrete verb ('Change') and scopes the resource narrowly to a lead's status or contact details, which separates it from siblings like dosai_update_contact or dosai_create_lead without naming them. It is clear what the tool mutates, though it never explicitly contrasts itself with those adjacent update tools.

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?

Usage is only implied: the note that status 'must be one the project defines' hints that status values come from project configuration (presumably dosai_get_lead_statuses), but the description never says to fetch them first or when to prefer this tool over dosai_update_contact. There are no explicit exclusions or alternative-routing sentences.

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