Skip to main content
Glama

lure_alerts

Retrieve recent bait-use alerts, newest first, and filter by severity or open status to check whether anyone has triggered a decoy credential.

Instructions

Recent alerts, newest first. Use this to answer 'has anyone used a bait?'.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
severityNoany
open_onlyNoonly alerts not yet marked investigated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses result ordering (newest first) and implies a read-only listing, but says nothing about read-only status, permissions, alert freshness/window, or what an alert record contains. The ordering hint is real added value, but most behavioral traits remain undisclosed.

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?

Two short sentences with the return content and ordering front-loaded, and no filler. The second sentence is a slightly colloquial framing but still earns its place by anchoring a use case.

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

Completeness2/5

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

For a three-parameter tool with no annotations, no output schema, and mostly undocumented parameters, the description is thin: it never explains the alert record shape, the severity semantics, or default paging behavior. An agent would have to guess at what comes back and how limit/severity change the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: open_only is documented in the schema, while limit and severity are not. The description adds no meaning for any parameter — it never mentions severity filtering, result caps, or what 'any' severity means — so it fails to compensate for the coverage gap.

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 description names the resource (alerts) and states the ordering ('newest first'), plus the question it answers, so an agent can tell it retrieves alert records. It does not use a crisp verb like 'list' and does not differentiate itself from siblings such as lure_acknowledge or lure_status, leaving the exact boundary implicit.

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?

It gives a concrete triggering question ('has anyone used a bait?'), which is clear context for selection. It stops short of any exclusion or pointer to a sibling (e.g., use lure_acknowledge to mark an alert investigated), so there is no when-not-to-use guidance.

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