Skip to main content
Glama
enkryptai

Enkrypt AI MCP Server

Official
by enkryptai

list_redteam_tasks

Retrieve and filter red team tasks by status using this tool to monitor and manage AI safety and prompt auditing activities in real-time.

Instructions

List all redteam tasks, optionally filtered by status.

Args: status: The status to filter tasks by (e.g., "Finished"). If None, list all tasks.

Returns: A dictionary containing the list of redteam tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo

Implementation Reference

  • The core handler function for the 'list_redteam_tasks' MCP tool. It is registered via the @mcp.tool() decorator and implements the tool logic by calling redteam_client.get_task_list(status=status) and returning the result as a dictionary. The input schema is defined by the function signature (optional 'status' string parameter) and docstring.
    @mcp.tool()
    def list_redteam_tasks(status: Optional[str] = None) -> Dict[str, Any]:
        """
        List all redteam tasks, optionally filtered by status.
    
        Args:
            status: The status to filter tasks by (e.g., "Finished"). If None, list all tasks.
    
        Returns:
            A dictionary containing the list of redteam tasks.
        """
        # List redteam tasks
        redteam_tasks = redteam_client.get_task_list(status=status)
    
        return redteam_tasks.to_dict()
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool lists tasks with optional filtering, which covers basic behavior, but lacks critical details such as pagination, rate limits, authentication requirements, error conditions, or whether the operation is read-only or has side effects. For a tool with no annotation coverage, this leaves significant gaps in understanding its operational characteristics.

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 well-structured and front-loaded, starting with the core purpose in the first sentence. The 'Args' and 'Returns' sections are clearly labeled and concise, with no redundant information. Every sentence earns its place by adding value, such as clarifying parameter behavior and return format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low schema description coverage, the description provides basic context but is incomplete. It covers the purpose and parameter usage adequately, but lacks details on behavioral traits, error handling, or output structure beyond 'a dictionary containing the list.' For a tool in this context, more comprehensive information would be beneficial to ensure correct usage.

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?

The input schema has 1 parameter with 0% description coverage, so the description must compensate. It explains the 'status' parameter as 'The status to filter tasks by (e.g., "Finished"). If None, list all tasks,' which adds meaningful semantics beyond the schema. However, it doesn't specify possible status values or formatting, leaving some ambiguity. With low schema coverage, this provides moderate but incomplete compensation.

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 clearly states the verb ('List') and resource ('all redteam tasks'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'get_redteam_task_details' or 'get_redteam_task_status' by focusing on listing multiple tasks rather than retrieving details about specific ones. However, it doesn't explicitly differentiate from other list tools like 'list_deployments' or 'list_models' beyond the resource type.

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 implies usage through the phrase 'optionally filtered by status,' suggesting this tool is for listing tasks with optional filtering. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'get_redteam_task_details' for specific tasks or 'get_redteam_task_status' for status checks. No exclusions or prerequisites are mentioned.

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

Related 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/enkryptai/enkryptai-mcp-server'

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