Skip to main content
Glama

adversarial_duelist

Fuzzes a Python function with null-byte, zero-division, overflow, and SQLi payloads to expose input-handling weaknesses before deployment.

Instructions

Offensive red-team fuzzer. Attacks a Python function with null-bytes, zero-divisions, overflow payloads, and SQLi vectors.

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": {
      "target_file": "<target_file>",
      "function_name": "<function_name>"
    },
    "name": "adversarial_duelist"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_fileYesPath to Python file
function_nameYesName of function to attack

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the entire behavioral burden, and it omits the most consequential fact: whether the target code is actually executed, and if so in what isolation. 'Attacks a Python function' strongly implies invocation of arbitrary user code, yet nothing is said about sandboxing, filesystem/network side effects, whether the target file is modified, or whether any report is produced. The payload list adds some useful context, but the risk profile of an offensive tool acting on a local file is undisclosed.

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 short sentences with the purpose and payload classes front-loaded and no filler. Every clause conveys information the agent cannot get from the name alone.

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 tool that runs offensive payloads against local Python code, with no annotations and no output schema, the description should explain what comes back (findings? crash report? pass/fail?) and what the operation does to the environment. Neither is covered, so an agent cannot anticipate results or side effects before invoking it.

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%, so both parameters ('Path to Python file', 'Name of function to attack') are already documented, and the baseline of 3 applies. The description adds no further meaning about path format, whether relative paths resolve, or how function_name is matched (exact, qualified, nested), leaving the schema to do all the work.

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 pair ('fuzzer' that 'attacks a Python function') and enumerates the payload classes (null-bytes, zero-divisions, overflow, SQLi), so an agent can tell this is a payload-injection fuzzer rather than a scanner or synthesizer. It stops short of explicitly contrasting itself with siblings such as blackbox_cloner or ghost_runner, but the resource scope (a Python function in a file) is distinctive enough to disambiguate.

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: 'Attacks a Python function' tells you the precondition (you need a target file and function name) but there is no when-to-use/when-not statement, no mention of prerequisites such as the file being importable or side-effect-free, and no named alternative for dynamic or black-box testing. An agent must infer the appropriate context.

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