Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Dismiss an insight

luca_insights_dismiss
DestructiveIdempotent

Dismiss one insight the coach does not want to act on. Use this rather than leaving it unread forever.

Instructions

Dismiss one insight the coach does not want to act on. Use this rather than leaving it unread forever.

Luca operation: POST /api/insights/{id}/dismiss 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": {
      "id": "<id>"
    },
    "name": "luca_insights_dismiss"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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

A3.8/5.0
Behavior4/5

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

The description adds genuine context beyond the annotations: required scopes (insights:write, luca:draft), redacted data sensitivity, a mandatory Idempotency-Key with server-generated fallback, and workspace override semantics. What it never states is reversibility, which matters given destructiveHint=true and the existence of a restore sibling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and selection hint lead, operational metadata follows in short labeled lines. The Luca operation, scopes, and sensitivity line are compact and each carries distinct information.

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?

Output schema exists, so return values need not be described, and the description covers auth, idempotency, and workspace targeting. The remaining gap is effect semantics — whether a dismissed insight can be recovered — which is the one thing an agent deciding to call a destructiveHint tool most needs.

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 75%, so baseline is 3. The description restates the idempotencyKey and workspace override behavior already documented in the schema, and adds nothing about the required `id` — the one parameter the schema leaves as bare format/pattern with no description.

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?

"Dismiss one insight" gives a specific verb plus resource, and "the coach does not want to act on" scopes intent. It never names its closest siblings (luca_insights_mark_read, luca_insights_mark_actioned), so the agent must infer the distinction between dismissing, reading, and actioning an insight.

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?

"Use this rather than leaving it unread forever" gives a reason to call it, but only relative to doing nothing. The real decision an agent faces is dismiss vs. mark_read vs. mark_actioned, and none of those alternatives are mentioned or excluded.

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