Skip to main content
Glama
badchars

living-off-the-land-lolbins-mcp-server

by badchars

search_techniques

Search living-off-the-land techniques by function, platform, ATT&CK ID, keyword, or combined filters. Returns matching entries with full details including stealth scores and detection coverage.

Instructions

Search LOL techniques by function, ATT&CK ID, platform, stealth score, catalog, keyword, detection coverage, or combined filters. Returns matching entries with full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesSearch mode
limitNoMax results to return
offsetNoPagination offset
catalogNoFor catalog mode: gtfobins, lolbas, loobins, loldrivers, lolrmm, etc.
filtersNoFor combined mode: apply multiple filters simultaneously
keywordNoFor keyword mode: free-text search across binary names, descriptions, commands
attck_idNoFor attck mode: T1059.006, T1548.001, etc.
functionNoFor function mode: shell, reverse_shell, download, upload, edr_disable, c2, etc.
platformNoFor platform mode or as additional filter
max_stealthNoFor stealth mode: max stealth score (1-5)
has_detectionNoFor detection_coverage mode: true=has rules, false=no coverage
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool returns matching entries but omits behavioral details such as pagination behavior, rate limits, data freshness, or whether results are exhaustive. The information provided is minimal beyond the obvious.

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 description is two sentences, front-loaded with the core action and supported criteria. No extraneous words, and every part adds value. Efficient use of space.

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?

Given the tool's complexity (11 parameters, nested objects, multiple modes), the description is too generic. It does not explain how modes work together, how combined filters are used, or what 'full details' means. Without an output schema, more context is needed for the agent to understand the response structure.

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

Parameters3/5

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

Schema description coverage is 100%, with each parameter having a brief description. The tool description adds no additional meaning beyond what is already in the schema. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches for LOL techniques by multiple criteria (function, ATT&CK ID, platform, etc.) and returns full details. It uses a specific verb 'Search' and resource 'LOL techniques', and implicitly differentiates from siblings by being a broad search tool.

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?

The description lists many search modes but does not explicitly state when to use this tool versus alternative sibling tools (e.g., find_defense_evasion). No guidance on when-not-to-use or preferred contexts is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/badchars/living-off-the-land-lolbins-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server