Skip to main content
Glama

lure_generate

Generates a fresh bait set in the manifest folder for new deployments, configured with listener, profile, and VPN count.

Instructions

Write a fresh bait set into the manifest's folder. Only use this for a new deployment; to replace an existing set use lure_rotate.

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": {
      "listener": "<listener>"
    },
    "name": "lure_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoit
listenerYeshost or IP of the machine that runs `lure listen`
vpn_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that this is a write/mutation and that replacement should use another tool, but it does not describe permissions, overwrite or side effects, idempotency, or what gets created.

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 definition is two sentences, front-loaded with the primary action and followed immediately by the usage constraint. There is no filler or redundant wording.

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 mutation tool with no annotations, no output schema, three parameters, and sparse parameter documentation, the description is too thin. It covers purpose and replacement routing but omits behavioral and parameter context needed for safe invocation.

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?

The description mentions no parameters at all. With only 33% schema description coverage, it leaves the profile enum and vpn_count semantics unexplained, so it does not compensate for the low schema coverage.

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 write action and resource: writing a fresh bait set into the manifest's folder. It also distinguishes this from replacement by naming lure_rotate. The domain terms 'bait set' and 'manifest's folder' are not explained, keeping it from being fully self-contained.

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

Usage Guidelines5/5

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

It explicitly limits use to a new deployment and directs replacement cases to lure_rotate, providing clear when-to-use and alternative guidance. The key routing decision is stated up front.

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