Skip to main content
Glama

lure_rotate

Rotate decoy credentials by replacing active baits with fresh ones while retaining retired baits in the manifest so they still trigger alerts.

Instructions

Replace the baits with fresh ones. Old baits stay in the manifest as retired and still alert.

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_rotate"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose one meaningful behavior: retired baits remain in the manifest and continue to alert, which tells the agent rotation is additive rather than a purge. It omits permissions, idempotency, whether new baits are auto-generated, and what happens to in-flight alerts.

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, front-loaded with the action and followed by the retention caveat. Slightly vague on scope ("the baits" — all of them or per profile?), but no wasted wording.

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 mutation with no annotations and no output schema, the description covers the action and one important retention behavior. It still leaves the agent without scope semantics for 'profile' or any expectation of what the call returns or triggers.

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 0% for the single optional 'profile' parameter, and the description never mentions it, so it is unclear whether rotation is global or scoped to one profile. The enum values (bank, home, hospital, it, office, plant) are readable but their effect on rotation is unexplained.

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?

"Replace the baits with fresh ones" gives a specific verb (replace) and resource (baits), so the core action is clear. It does not differentiate from siblings such as lure_baits or lure_generate, so an agent must still infer why rotation exists as a separate operation.

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

Usage Guidelines2/5

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

There is no statement of when to rotate versus when to add baits, regenerate them, or check status. The only contextual sentence describes a side effect, not a usage condition, leaving the agent to guess the trigger for this tool.

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