Skip to main content
Glama
io.github.kushvinth/crowbar

io.github.kushvinth/crowbar

cb_nuclei

Search Nuclei templates by query and domain to retrieve YAML file paths for exact matchers, enabling targeted vulnerability checks.

Instructions

Search Nuclei templates; returns YAML paths for exact matchers.

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": {
      "query": "<query>"
    },
    "name": "cb_nuclei"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
domainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

C2.6/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 only states that YAML paths are returned; it does not confirm this is a read-only lookup, say whether results are paged or capped, or explain what 'exact matchers' means for result contents.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no wasted words, which is good. However, the brevity tips into under-specification: the one clause beyond the purpose, 'for exact matchers,' is opaque and consumes space without adding usable meaning.

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 three-parameter search tool with no annotations, no enum constraints, and no output schema, the description should explain query syntax, the role of domain, and result shape. It only gestures at the return value, leaving the two optional parameters entirely unexplained.

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% across three parameters, so the description must compensate and does not. It never explains what 'query' accepts (template name, matcher string, keyword), what 'domain' scopes, or that 'limit' defaults to 20 and is capped at 100 — all of which an agent needs to craft a valid query.

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 names a specific verb and resource ('Search Nuclei templates') and adds what comes back ('returns YAML paths'), so an agent knows the tool's domain. The trailing qualifier 'for exact matchers' is ambiguous and is not clarified anywhere, though the core purpose is unmistakable.

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 when-to-use or when-not-to-use guidance, and no mention of how this differs from the many other cb_* lookup tools. The agent must infer that this is the Nuclei-template-specific search rather than a general keyword search such as cb_search.

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