Skip to main content
Glama
Sign In
NullSec-RedTeam-AI

NullSec-RedTeam-AI

by Panda1847
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_available_tools

Discover every authorized security tool available in the red-team environment. Instantly view tool names and descriptions to select the right capability for your campaign.

Instructions

List all available security tools with descriptions.

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": "list_available_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv7.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description must fully convey behavioral traits. It only states 'list all available security tools with descriptions,' omitting crucial details such as whether the operation is read-only, if pagination applies, or any authorization requirements. The agent cannot infer safety or side-effect profile from this minimal text.

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 a single, front-loaded sentence of five words that immediately communicates the tool's core action. No wasted words; every part is essential.

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?

Given the tool has zero parameters and an output schema (not shown), the description is mostly complete for a simple listing tool. It could benefit from mentioning the output format (e.g., an array of tool names and descriptions) to reduce uncertainty, but the current text is sufficient for basic understanding.

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 input schema has zero parameters and 100% schema coverage, so the baseline is 4. The description adds value by clarifying the purpose beyond the empty schema, but no parameter-level detail is needed.

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 verb 'List' and the resource 'security tools with descriptions,' making the tool's purpose immediately obvious. It distinguishes itself from sibling tools like run_security_tool and get_job_status by focusing on listing rather than execution or status checks.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't suggest using this tool before run_security_tool to discover available options, nor does it indicate when not to use it. The description lacks contextual cues for appropriate use.

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

Deploy Server

Other Tools