Skip to main content
Glama

lure_record

Record where a bait file or username is planted so alerts identify the exact host and path. Capture bait and location details to support incident response.

Instructions

Record where a bait was actually planted, so alerts name the exact place.

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": {
      "bait": "<bait>",
      "location": "<location>"
    },
    "name": "lure_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
baitYesbait file name or username
locationYeshost and path, e.g. FIN-WS-07:C:\Users\admin\Desktop

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. It usefully discloses the downstream effect that alerts will name the exact planted location, but for a mutation tool it does not say whether records are created or overwritten, whether duplicates are allowed, what permissions are required, or what happens if the bait does not exist.

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?

The description is a single front-loaded sentence with no wasted wording. It states the action first and then gives the downstream purpose, making it suitably sized for a simple two-parameter tool.

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?

The tool is simple and the input schema is fully documented, but the description does not cover mutation semantics, prerequisites, duplicate handling, or relationships to sibling tools. For a record-style operation with no annotations, it is adequate but has clear gaps.

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 100%, and the schema already documents both bait and location with format examples. The description restates the location concept but adds no parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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 states a specific verb and resource: recording where a bait was actually planted. That is clearly distinct from siblings like status, alerts, generate, and rotate, though it does not explicitly differentiate itself from them.

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?

The phrase 'actually planted' implies the tool is used after deployment or confirmation of a bait's real location. However, it gives no explicit when-to-use guidance, no prerequisites, and no comparison to alternatives such as lure_generate or lure_baits.

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