Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a channel account

luca_channels_get
Read-onlyIdempotent

Fetch a channel account by ID to inspect its status, health, cleanup state after disconnect, and available coach actions.

Instructions

Read one channel account: status, health, cleanup state after a disconnect, and the actions the coach can take on it. Older rows stay readable by ID.

Luca operation: GET /api/channels/{id} Required scopes: channels: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

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

Input Schema

NameRequiredDescriptionDefault
idYes
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.2
    • addedOutput schema / properties / result / properties / campaignReady
      Added value: +{
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv0.4.1
    • addedOutput schema / properties / result / properties / aiDmAutoSendActive
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / result / properties / aiDmAutoSendEnabled
      Added value: +{
+  "type": "boolean"
+}
  3. 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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new operational context: required scopes (channels:read, luca:read), 'data sensitivity: redacted', historical-row readability, and the workspace-default override rule.

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?

Front-loaded purpose sentence followed by short labeled metadata lines; nearly every line carries usable information. 'Does not require idempotency' is somewhat redundant and mildly confusing next to idempotentHint=true, but it is a single short line.

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?

An output schema exists, so return-value documentation is not needed, and auth/scopes/sensitivity are all covered. What remains thin is failure behavior (e.g., what happens for an unknown or deleted channel ID) and the explicit relationship to the list tool.

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%; the two workspace parameters are already documented in the schema, and the description only reinforces their override behavior against the environment-configured default. The required `id` parameter carries format/pattern in the schema but no description, and 'older rows stay readable by ID' is the only added meaning.

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 first sentence gives a specific verb and resource ('Read one channel account') and enumerates the returned facets: status, health, cleanup state after a disconnect, and available coach actions. The singular 'one' plus 'by ID' implicitly separates it from luca_channels_list, though no sibling is named explicitly.

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 context is implied rather than stated: 'Older rows stay readable by ID' hints you can fetch historical channels, and the workspace-override sentence tells you which parameter wins over the environment default. There is no explicit when-to-use versus when-to-use-a-list/sibling guidance or any exclusion.

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