Skip to main content
Glama
enkryptai

Enkrypt AI MCP Server

Official
by enkryptai

get_redteam_task_status

Retrieve the status of a red team task using test name to monitor AI safety analysis and prompt auditing progress on the Enkrypt AI MCP Server.

Instructions

Get the status of a redteam task.

Args: test_name: The name of the redteam test.

Returns: A dictionary containing the status of the redteam task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
test_nameYes

Implementation Reference

  • The handler function for the 'get_redteam_task_status' MCP tool. It is decorated with @mcp.tool() which handles registration with the FastMCP server. The function takes a test_name parameter, calls redteam_client.status(test_name=test_name), and returns the result as a dictionary. Type hints and docstring provide the input/output schema.
    @mcp.tool()
    def get_redteam_task_status(test_name: str) -> Dict[str, Any]:
        """
        Get the status of a redteam task.
    
        Args:
            test_name: The name of the redteam test.
    
        Returns:
            A dictionary containing the status of the redteam task.
        """
        # Get redteam task status
        redteam_task_status = redteam_client.status(test_name=test_name)
    
        return redteam_task_status.to_dict()
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions returning a dictionary but doesn't disclose what the status includes (e.g., running, completed, failed), whether it's read-only, if authentication is needed, or any rate limits. This leaves significant gaps for a tool that likely interacts with sensitive redteam tasks.

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 front-loaded with the core purpose, followed by structured Args and Returns sections. Every sentence earns its place with no wasted words, making it efficiently sized and easy to parse for an AI agent.

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 complexity of redteam tasks, no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on status values, error handling, permissions, or how it integrates with sibling tools like 'add_redteam_task', making it inadequate for safe and effective use in this context.

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 0%, so the description must compensate. It adds that 'test_name' is 'The name of the redteam test', providing basic semantics beyond the schema's title 'Test Name'. However, it doesn't clarify format, examples, or constraints (e.g., case sensitivity, allowed characters), leaving the parameter partially documented.

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 ('Get') and resource ('status of a redteam task'), making the purpose specific and understandable. It distinguishes from siblings like 'get_redteam_task_details' and 'get_redteam_task_results_summary' by focusing specifically on status rather than details or results, though the distinction could be more explicit.

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 like 'get_redteam_task_details' or 'list_redteam_tasks'. The description only states what it does without context about prerequisites, timing, or comparisons to sibling tools, leaving the agent to infer usage scenarios.

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