Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read the coach's voice fingerprint

luca_voice_profile
Read-onlyIdempotent

Retrieves a coach's voice-profile summary—reply style, example counts, refresh data, and drafting brief—to guide on-brand reply drafting without exposing corpus text.

Instructions

Read a non-verbatim voice-fingerprint summary: version, example count, last refresh, the measured style of the coach's replies, and the short brief Luca drafts from. A model writes the brief from those replies, and a redacted-tier key reads it as null. No corpus text.

Luca operation: GET /api/voice/profile Required scopes: voice: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

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_voice_profile"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.2
    • addedOutput schema / properties / provenance
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "note": {
+      "type": "string"
+    },
+    "untrusted": {
+      "enum": [
+        true
+      ],
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "untrusted",
+    "note"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / result / properties / brief
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / result / properties / style
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {
+        "capitalization": {
+          "type": "string"
+        },
+        "contractionRate": {
+          "type": "number"
+        },
+        "dominantLanguage": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "emojiRate": {
+          "type": "number"
+        },
+        "lengthChars": {
+          "additionalProperties": true,
+          "properties": {
+            "median": {
+              "type": "number"
+            },
+            "p25": {
+              "type": "number"
+            },
+            "p75": {
+              "type": "number"
+            }
+          },
+          "type": "object"
+        },
+        "questionRate": {
+          "type": "number"
+        },
+        "sampleCount": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "signOffRate": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / result / x-luca-redacted-fields
      Added value: +[
+  "brief"
+]
  2. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, closed-world, and non-destructive, and the description adds genuinely new behavior: the brief is model-written, redacted-tier keys receive null, and no corpus text is exposed. It also discloses required scopes and the default-workspace behavior. The only weak spot is restating 'Does not require idempotency', which the idempotentHint annotation already conveys.

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 substantive sentence is front-loaded and dense with useful detail, followed by compact operational metadata (endpoint, scopes, sensitivity, idempotency). Slightly wasteful in repeating the idempotency fact already carried by annotations, but overall no padded prose.

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 zero-required-parameter read tool with an output schema and full annotation coverage, this is close to complete: it covers what is read, what is deliberately excluded, redaction behavior, and workspace scoping. The remaining gap is routing guidance relative to sibling read tools such as luca_voice_corpus.

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?

Schema coverage is 100% and both parameters are self-documented, so the baseline would be 3. The description earns more by explaining that workspaceId/workspaceSlug override a default workspace configured by the environment — context the schema does not provide.

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 states a specific verb and resource ('Read a non-verbatim voice-fingerprint summary') and enumerates the returned contents: version, example count, last refresh, measured reply style, and the drafted brief. The line 'No corpus text' explicitly separates it from luca_voice_corpus, so an agent can distinguish the two without opening either schema.

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 implied rather than stated: the agent can infer this is for reading the derived profile instead of the raw corpus, and the workspace override note gives operational context. But there is no explicit 'use this when...' guidance or a named alternative for cases where the caller actually wants underlying replies.

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