Skip to main content
Glama

Correct a captured lead

lead_update
DestructiveIdempotent

Changes one captured lead: captured field values (e.g. a misheard city), the name, the notes, or its pipeline status (NEW, CONTACTED, QUALIFIED, CONVERTED, LOST, JUNK). Only what is passed changes; a field is never removed ("" blanks one). The phone number and call details cannot be changed. A copy already in a CRM (e.g. Zoho) is not updated, and the reply says so.

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": {
      "captureId": "<captureId>"
    },
    "name": "lead_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe lead's name
notesNo
dryRunNoIf true, return what would be sent without saving
fieldsNoCaptured field values to set, e.g. {"City":"Pune"}. Keys are the lead's captured field names.
statusNoPipeline status
captureIdYesThe lead's id (lead_id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / captureId / description
      Previous value: -"The lead's id (lead_id from lead_list or lead_detail)"New value: +"The lead's id (lead_id)"
    • changedInput schema / properties / fields / description
      Previous value: -"Captured field values to set, e.g. {\"City\":\"Pune\"}. Keys as lead_detail shows them under \"captured\"."New value: +"Captured field values to set, e.g. {\"City\":\"Pune\"}. Keys are the lead's captured field names."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the flags (destructive, idempotent, not read-only); the description goes well beyond them with partial-update semantics, the fact that omitted fields are untouched, that a field is never deleted but "" blanks it, and that phone number and call details are immutable. It also discloses a downstream side effect (external CRM not synced, and the reply says so), which an agent could not infer from structured data.

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 sentences, front-loaded with the mutable surface, then the partial-update rule, then the immutables, then the CRM caveat — each sentence carries distinct decision-relevant information with no restatement of the name or title.

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 six-parameter mutation tool with a nested object and no output schema, the description covers mutability, immutability, and the one notable response caveat. Minor gaps remain: no mention of what `dryRun` is for at the description level and no note on whether status transitions are validated (e.g. LOST back to NEW).

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?

With 83% schema coverage the baseline is 3, and the description earns above that by explaining the `fields` JSON shape via a concrete example and listing all six status values, plus the empty-string convention that the schema does not state. It does not cover `dryRun` or `captureId`, leaving those entirely to the schema.

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?

"Changes one captured lead" gives a specific verb plus resource and scope, then enumerates exactly which parts are mutable (field values, name, notes, status). That enumeration plus the explicit immutables (phone number, call details) makes it trivially separable from lead_create and lead_detail without opening any schema.

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?

The description clearly frames the situation (correcting a captured lead, e.g. a misheard city) and sets boundaries on when the tool is insufficient (CRM copies like Zoho are not updated). It does not name an alternative tool for those out-of-scope cases, so it stops short of full when-to-use/when-not routing.

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.