Skip to main content
Glama

lure_status

Summarize bait set status, including bait counts, used baits, open alerts, and attacker paths by source address to support incident triage.

Instructions

Summary of the bait set: how many baits, which have been used, open alerts, and the attacker's path per source address.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full burden, and it does disclose the returned content (counts, used status, open alerts, per-source attacker path), which is the most valuable behavioral fact here. It does not state that the call is side-effect free or read-only, nor anything about cost, freshness, or format of the returned summary.

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?

One sentence, front-loaded with the 'summary' framing and followed by the enumerated contents. Every clause maps to something the agent gets back, with no filler.

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?

For a zero-parameter status tool with no annotations and no output schema, the description compensates by listing the fields the summary returns, which is the main gap it needed to close. It stops short of describing the shape of 'attacker's path per source address' or the time window covered, which leaves a little ambiguity.

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 and the schema is closed, so there is nothing for the description to disambiguate. Baseline 4 for a parameterless tool is appropriate.

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 concretely enumerates what the summary contains: bait count, used baits, open alerts, and attacker path per source address. That is specific enough to distinguish it from list-style siblings like lure_baits or lure_alerts, though it never explicitly names those siblings or states the verb ('retrieve a status summary').

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 explicit when-to-use guidance, no prerequisite conditions, and no routing to alternatives such as lure_alerts for alert detail or lure_baits for per-bait detail. An agent can infer that this is an overview tool, but the inference is left entirely to it.

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