Skip to main content
Glama
enkryptai

Enkrypt AI MCP Server

Official
by enkryptai

add_deployment

Add a new deployment with custom configuration in the Enkrypt AI MCP Server, specifying input and output guardrails policies to manage AI safety and detection rules.

Instructions

Add a new deployment using the provided configuration.

Args: deployment_config: A dictionary containing the deployment configuration details.

Example Usage:
{
    "deployment_config": {
        sample_deployment_config = {
        "name": deployment_name,
        "model_saved_name": model_saved_name,
        "input_guardrails_policy": {
            "policy_name": policy_name,
            "enabled": True,
            "additional_config": {
                "pii_redaction": False  #Add these if any additional detectors than that in the policy are needed
            },
            "block": [
                "injection_attack",    # Could be any of the active detectors (Ask user if they want to block)
                "policy_violation"
            ]
        },
        "output_guardrails_policy": {
            "policy_name": policy_name,
            "enabled": False,
            "additional_config": {
                "hallucination": False,  #Add these if any additional detectors than that in the policy are needed
                "adherence": False,
                "relevancy": False
            },
            "block": [
                "nsfw"    # Could be any of the active detectors (Ask user if they want to block)
            ]
        },
    }
}

Always ask user if they want to block any of the detectors in the policy for both input and output. (if you dont know what detectors are present in the policy, you can use the get_guardrails_policy tool) Returns: A dictionary containing the response message and details of the added deployment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployment_configYes

Implementation Reference

  • The handler function for the 'add_deployment' MCP tool. It is decorated with @mcp.tool() for registration and calls the deployment_client to add a deployment based on the provided config, returning the response as a dictionary. The docstring provides detailed input schema examples.
    @mcp.tool()
    def add_deployment(deployment_config: Dict[str, Any]) -> Dict[str, Any]:
        """
        Add a new deployment using the provided configuration.
    
        Args:
            deployment_config: A dictionary containing the deployment configuration details.
    
            Example Usage:
            {
                "deployment_config": {
                    sample_deployment_config = {
                    "name": deployment_name,
                    "model_saved_name": model_saved_name,
                    "input_guardrails_policy": {
                        "policy_name": policy_name,
                        "enabled": True,
                        "additional_config": {
                            "pii_redaction": False  #Add these if any additional detectors than that in the policy are needed
                        },
                        "block": [
                            "injection_attack",    # Could be any of the active detectors (Ask user if they want to block)
                            "policy_violation"
                        ]
                    },
                    "output_guardrails_policy": {
                        "policy_name": policy_name,
                        "enabled": False,
                        "additional_config": {
                            "hallucination": False,  #Add these if any additional detectors than that in the policy are needed
                            "adherence": False,
                            "relevancy": False
                        },
                        "block": [
                            "nsfw"    # Could be any of the active detectors (Ask user if they want to block)
                        ]
                    },
                }
            }
    
        Always ask user if they want to block any of the detectors in the policy for both input and output. (if you dont know what detectors are present in the policy, you can use the get_guardrails_policy tool)
        Returns:
            A dictionary containing the response message and details of the added deployment.
        """
        # Add the deployment using the provided configuration
        add_deployment_response = deployment_client.add_deployment(deployment_config)
    
        # Return the response as a dictionary
        return add_deployment_response.to_dict()
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool creates a new deployment (a write operation) and mentions behavioral aspects like asking users about blocking detectors and referencing another tool for policy info. However, it doesn't cover critical details like required permissions, rate limits, idempotency, or error handling, leaving significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose and poorly structured. The example usage is embedded with comments and incomplete syntax (e.g., 'sample_deployment_config =' inside the JSON), making it confusing. Key information is buried in comments rather than front-loaded. Sentences like 'Always ask user...' are important but could be more concise.

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 (1 parameter with nested objects, no output schema, no annotations), the description is insufficient. It provides an example but lacks a clear explanation of the deployment concept, expected return values (only vaguely mentions 'response message and details'), error cases, or dependencies. For a tool that likely involves significant configuration, this leaves too much ambiguity.

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

Parameters2/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 provides an example with nested configuration details (name, model_saved_name, guardrails policies), which adds meaningful context beyond the generic 'object' type in the schema. However, it doesn't explain all possible fields or constraints (e.g., required vs. optional, data types, validation rules), leaving the parameter documentation incomplete.

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 tool's purpose: 'Add a new deployment using the provided configuration.' It specifies the verb ('Add') and resource ('deployment'), distinguishing it from siblings like 'modify_deployment_config' or 'remove_deployment'. However, it doesn't explicitly differentiate from 'add_agent' or 'add_model' in terms of what type of resource it creates.

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 includes implicit guidance: 'Always ask user if they want to block any of the detectors in the policy for both input and output' and references the 'get_guardrails_policy' tool for policy details. However, it lacks explicit when-to-use vs. alternatives (e.g., when to use 'add_deployment' vs. 'modify_deployment_config' or prerequisites). The guidance is more about implementation details than tool selection.

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