Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update alert delivery settings

luca_insights_settings_update
DestructiveIdempotent

Merge-patch the coach's alert-delivery settings. Send only what you are changing; anything left out keeps its current value.

Instructions

Merge-patch the coach's alert-delivery settings. Send only what you are changing; anything left out keeps its current value.

Luca operation: PUT /api/insights/settings Required scopes: insights:write Required OAuth scope: luca:draft; data sensitivity: redacted Requires Idempotency-Key. Provide idempotencyKey for safe retries, or the server will generate one. 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": {
      "body": "<body>"
    },
    "name": "luca_insights_settings_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.
idempotencyKeyNoStable key for safe retries. If omitted, the MCP server generates a unique key for this call.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses required scopes ('insights:write', 'luca:draft'), data sensitivity ('redacted'), idempotency-key behavior, and merge-patch semantics. These details add substantial operational context not captured by the structured annotations alone.

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 description is front-loaded with the core merge-patch instruction and is generally efficient. The operation path, scope lines, and idempotency note are useful but somewhat boilerplate; they earn their place for transparency but add length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the annotations, output schema, and nested input schema, the description covers all essential invocation details: merge semantics, required scopes, idempotency handling, and workspace override. Nothing critical for correct invocation is missing.

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 75% schema description coverage, the schema already documents workspaceId, workspaceSlug, and idempotencyKey. The description adds important meaning for the body parameter by explaining merge-patch behavior ('send only what you are changing'), which is not evident from the schema's nested object structure.

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: 'Merge-patch the coach's alert-delivery settings.' This clearly identifies the operation and distinguishes it from the read-only sibling luca_insights_settings_get, which retrieves rather than patches settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage context: 'Send only what you are changing; anything left out keeps its current value.' It also explains workspace override and idempotency key usage. However, it does not explicitly name alternatives or state when not to use this tool versus settings_get.

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