Skip to main content
Glama

lure_baits

Retrieve live bait records—files, usernames, services, planting locations, and trigger status—to track decoy deployments and identify activated baits without exposing passwords.

Instructions

Every live bait: file, username, service, where it is meant to be planted, where it was recorded as planted, and whether it has been triggered. Passwords are never returned.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 burden. It does disclose two valuable behavioral facts: the record shape (planted location vs. recorded plant location vs. trigger state) and an explicit security guarantee that passwords are never returned. Still missing are auth requirements, ordering, pagination/volume limits, and whether non-live or rotated baits are excluded.

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?

Two sentences with no filler; the payload scope is front-loaded and the security constraint is stated as a short trailing guarantee. Every clause carries information.

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

Completeness4/5

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

With zero params, no output schema, and no annotations, the description must substitute for the return-value documentation, and it does so by enumerating the fields. Gaps remain around volume, ordering, and what exactly "live" excludes, but the core is covered.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to document and the baseline is 4. The listed attributes describe the response shape rather than inputs, which is appropriate here but adds nothing to parameter understanding.

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?

"Every live bait" states the resource and scope (all live baits) and the field enumeration makes clear this is a full inventory read rather than a single-record lookup. The retrieval verb is implicit rather than stated, and no sibling tool is named for contrast, so it stops short of a 5.

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 only implied: the word "Every" signals a broad inventory listing, contrasting in spirit with single-target siblings like lure_status or lure_acknowledge. There is no explicit when-to-use, when-not-to-use, or named alternative, leaving the agent to infer routing.

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