Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Explain why a lead qualified

luca_leads_explain
Read-onlyIdempotent

Explain why a lead qualified: the qualifier's reasoning, signals, and confidence from its most recent drafted turn.

Instructions

Explain why a lead qualified: the qualifier's reasoning, signals, and confidence from its most recent drafted turn.

Luca operation: GET /api/leads/{id}/explain Required scopes: leads:read Required OAuth scope: luca:read; data sensitivity: full_content Does not require idempotency. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

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": {
      "id": "<id>"
    },
    "name": "luca_leads_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "at": {
-        "type": "string"
-      },
-      "confidence": {
-        "type": "number"
-      },
-      "leadId": {
-        "type": "string"
-      },
-      "qualification": {},
-      "status": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {
-      "leadId": {
-        "type": "string"
-      },
-      "reason": {
-        "type": "string"
-      },
-      "status": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "at": {
+        "type": "string"
+      },
+      "confidence": {
+        "type": "number"
+      },
+      "leadId": {
+        "type": "string"
+      },
+      "qualification": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "number"
+          },
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "object"
+          },
+          {
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "leadId": {
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
  2. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive traits, but the description adds real operational context: required scopes (leads:read, luca:read), data sensitivity of full_content, explicit 'does not require idempotency', and workspace override behavior. This is meaningful added value beyond the annotations.

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?

The core purpose is front-loaded in the first sentence, then structured metadata (operation, scopes, idempotency, workspace) follows. Slightly dense with metadata but every section is scoped and non-redundant; not verbose.

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 read-only retrieval tool with an output schema present, the description covers what it returns, auth scopes, data sensitivity, and workspace override. The one gap is that the required 'id' parameter's meaning is left implicit rather than stated as the lead identifier.

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 67%, so the schema documents the workspace parameters. The description implies the 'id' is a lead id via the endpoint path but does not explicitly define it, and workspace override guidance largely mirrors the schema. Adding some value over the schema but not compensating 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?

States a specific verb ('Explain'), resource ('why a lead qualified'), and even describes returned content: reasoning, signals, confidence from the most recent drafted turn. It does not explicitly distinguish itself from the similarly named sibling luca_review_queue_explain, so a strong 4 rather than 5.

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?

The purpose implies when to use (retrieving qualification reasoning for a specific lead), but there is no explicit when-to-use guidance, no mention of prerequisites, and no comparison to alternatives like luca_review_queue_explain.

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

Deploy Server

Other Tools