Skip to main content
Glama

Set lead source

set_lead_sources
DestructiveIdempotent

Create or update a workspace lead source: set its label and active state by key (built-in or custom, lowercase_with_underscores). Idempotent — re-sending the same key updates it. Archiving the fallback 'other' source is not allowed. Use list_lead_sources to see current sources. The result echoes the operating workspace.

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": {
      "isActive": "<isActive>",
      "key": "<key>",
      "label": "<label>"
    },
    "name": "set_lead_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesStable source key, lowercase_with_underscores (built-in or custom).
labelYesHuman-readable label shown for this source in the UI.
isActiveYesWhether the source is selectable for new leads. Set false to archive it (the fallback 'other' source cannot be archived).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changed
    • addedInput schema / properties / isActive / description
      Added value: +"Whether the source is selectable for new leads. Set false to archive it (the fallback 'other' source cannot be archived)."
    • addedInput schema / properties / key / description
      Added value: +"Stable source key, lowercase_with_underscores (built-in or custom)."
    • addedInput schema / properties / label / description
      Added value: +"Human-readable label shown for this source in the UI."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description adds meaningful behavioral context beyond the annotations: idempotency semantics, the restriction on archiving the 'other' source, and the result echoing the workspace. Since the annotations only declare idempotent and destructive hints, the description elaborates on what these mean in practice. No contradiction detected.

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?

The description is composed of five short, purposeful sentences, each conveying a distinct piece of information: purpose, idempotency, constraint, alternative, and result. It is front-loaded with the main action and contains no unnecessary words.

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?

The tool is relatively simple with only three parameters, and the description covers the essential behavior, constraints, and result. Since there is no output schema, the note that the result echoes the operating workspace is valuable, though it could be slightly more explicit about the response format. Overall, it is sufficient for an agent to invoke the tool correctly.

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 100% schema description coverage, the baseline is 3. The description adds value by framing key as the identifier and label/isActive as mutable state, and by noting that re-sending the same key updates the source. This goes slightly beyond the schema, which already documents each field individually.

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 clearly states that the tool creates or updates a workspace lead source, specifying the label and active state by key. It also explicitly points to list_lead_sources for seeing current sources, distinguishing it from sibling tools. The mention of built-in/custom keys and the fallback 'other' source further clarifies its purpose.

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?

The description provides explicit guidance on when to use this tool (create/update) and points to the alternative list_lead_sources for viewing sources. It also includes important usage constraints, such as the inability to archive the fallback 'other' source. The idempotency note tells the agent that re-sending the same key is safe.

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