Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read the coach's niche profile

luca_coach_niche_profile
Read-onlyIdempotent

Read the coach's offer, audience, price range, promised outcomes, disqualifiers, and FAQs. This is the context that decides whether a lead is a fit.

Instructions

Read the coach's offer, audience, price range, promised outcomes, disqualifiers, and FAQs. This is the context that decides whether a lead is a fit.

Luca operation: GET /api/coaches/niche-profile Required scopes: coach:read Required OAuth scope: luca:read; data sensitivity: redacted Does not require idempotency. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "luca_coach_niche_profile"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
resultYes

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": {
-      "audience": {
-        "type": "string"
-      },
-      "callToAction": {
-        "type": "string"
-      },
-      "defaultLanguage": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "disqualifiers": {
-        "type": "array"
-      },
-      "faqs": {
-        "type": "array"
-      },
-      "guarantees": {
-        "type": "array"
-      },
-      "languages": {
-        "type": "array"
-      },
-      "niche": {
-        "type": "string"
-      },
-      "objections": {
-        "type": "array"
-      },
-      "offer": {
-        "type": "string"
-      },
-      "offers": {
-        "type": "array"
-      },
-      "outcomes": {
-        "type": "array"
-      },
-      "priceRange": {
-        "type": "string"
-      },
-      "profileUpdatedAt": {
-        "type": "string"
-      },
-      "sellFramework": {
-        "additionalProperties": true,
-        "properties": {
-          "customGuidance": {
-            "type": "string"
-          },
-          "customStages": {
-            "type": "array"
-          },
-          "id": {
-            "type": "string"
-          },
-          "objectionPriorityOverride": {
-            "type": "array"
-          },
-          "overrides": {
-            "type": "array"
-          }
-        },
-        "type": "object"
-      },
-      "sensitivity": {
-        "type": "string"
-      },
-      "testimonials": {
-        "type": "array"
-      },
-      "toneBoundaries": {
-        "type": "array"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "audience": {
+        "type": "string"
+      },
+      "bookingUrl": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "callMinutes": {
+        "anyOf": [
+          {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "callToAction": {
+        "type": "string"
+      },
+      "defaultLanguage": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "disqualifiers": {
+        "type": "array"
+      },
+      "faqs": {
+        "type": "array"
+      },
+      "guarantees": {
+        "type": "array"
+      },
+      "languages": {
+        "type": "array"
+      },
+      "niche": {
+        "type": "string"
+      },
+      "objections": {
+        "type": "array"
+      },
+      "offer": {
+        "type": "string"
+      },
+      "offers": {
+        "type": "array"
+      },
+      "outcomes": {
+        "type": "array"
+      },
+      "priceRange": {
+        "type": "string"
+      },
+      "profileUpdatedAt": {
+        "type": "string"
+      },
+      "sellFramework": {
+        "additionalProperties": true,
+        "properties": {
+          "customGuidance": {
+            "type": "string"
+          },
+          "customStages": {
+            "type": "array"
+          },
+          "id": {
+            "type": "string"
+          },
+          "objectionPriorityOverride": {
+            "type": "array"
+          },
+          "overrides": {
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "sensitivity": {
+        "type": "string"
+      },
+      "testimonials": {
+        "type": "array"
+      },
+      "toneBoundaries": {
+        "type": "array"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  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 declare read-only, idempotent, non-destructive, and closed-world behavior. The description usefully adds the HTTP operation, required OAuth scopes, and the redacted data sensitivity, which are important context beyond the annotations. It does not describe rate limits or return behavior, but the output schema likely covers the latter.

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 purpose and returned fields are front-loaded, and the operational details are grouped afterward. It is generally tight, though the idempotency line is somewhat redundant with the annotations and the description could be slightly shorter.

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 low-complexity read-only tool with only two optional parameters and an existing output schema, the description supplies the necessary operational details: operation, scopes, sensitivity, and workspace override behavior. Its main gap is not clarifying its relationship to similarly named coach niche/profile siblings.

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 coverage is 100%, so both optional workspace parameters are already documented in the schema. The description adds that they override the default workspace configured by the environment, but it does not clarify precedence if both are supplied, so the added value is modest.

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 clearly states a specific read operation and enumerates the exact content returned: offer, audience, price range, promised outcomes, disqualifiers, and FAQs. It does not explicitly differentiate this tool from closely named siblings such as luca_coach_niche or luca_coach_profile, so it stops short of a 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?

It gives a clear use context by saying this is the context that decides whether a lead is a fit. However, it does not say when to use this tool instead of related coach-profile or niche tools, nor does it provide exclusions or prerequisites beyond required scopes.

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