Skip to main content
Glama

lure_acknowledge

Marks an alert as investigated using its ID from lure_alerts, helping agents track which incidents have been reviewed.

Instructions

Mark an alert as investigated by its id (from lure_alerts).

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": "lure_acknowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only says the alert becomes 'investigated'. It does not say whether the operation is idempotent, reversible, whether the alert disappears from lure_alerts results, whether permissions are required, or what error surfaces for an unknown id.

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?

A single front-loaded sentence with the action first and the id provenance in parentheses; nothing is wasted or repetitive.

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

Completeness3/5

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

For a one-parameter state-changing tool with no annotations and no output schema, the description covers the action and where to get the id, but leaves out the outcome of the call and the post-acknowledgment state an agent would need to reason about next steps.

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 0% and the single parameter is described only as an id, so the schema adds nothing. The description does add real value by pointing to lure_alerts as the source of that id, but it does not state the id's type or format (integer, as the schema shows) or behavior for a nonexistent id.

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?

States a specific verb and state change ('Mark an alert as investigated') on a specific resource ('alert'), and identifies the id's provenance ('from lure_alerts'), which lets an agent distinguish this write action from the sibling listing tool lure_alerts.

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: call this after investigating an alert, using an id obtained from lure_alerts. There is no explicit statement of when not to use it, no mention of what happens if the alert is already acknowledged, and no named alternative for un-marking or dismissing an alert.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.