Skip to main content
Glama
enkryptai

Enkrypt AI MCP Server

Official
by enkryptai

modify_deployment_config

Update and adjust deployment configurations, including guardrail policies and model settings, to ensure AI safety and compliance. Modify settings like input/output guardrails, detector blocks, and additional configurations for tailored deployment management.

Instructions

Modify the deployment configuration and update the deployment.

Args: deployment_name: The name of the deployment to be modified. new_deployment_config: The new deployment configuration to be modified.

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)
            ]
        },
    }
}

Returns: A dictionary containing the response message and details of the modified deployment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployment_nameYes
new_deployment_configYes

Implementation Reference

  • The handler function for the 'modify_deployment_config' MCP tool. Decorated with @mcp.tool() for automatic registration and schema inference from type hints and docstring. Modifies the deployment config using deployment_client and returns the result as a dict.
    @mcp.tool()
    def modify_deployment_config(deployment_name: str, new_deployment_config: Dict[str, Any]) -> Dict[str, Any]:
        """
        Modify the deployment configuration and update the deployment.
    
        Args:
            deployment_name: The name of the deployment to be modified.
            new_deployment_config: The new deployment configuration to be modified.
    
            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)
                        ]
                    },
                }
            }
    
        Returns:
            A dictionary containing the response message and details of the modified deployment.
        """
        # Modify the deployment using the provided configuration
        modify_deployment_response = deployment_client.modify_deployment(deployment_name=deployment_name, config=new_deployment_config)
    
        # Return the response as a dictionary
        return modify_deployment_response.to_dict()
  • The @mcp.tool() decorator registers the modify_deployment_config function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'modify' and 'update' imply mutation, it doesn't specify permissions required, whether changes are reversible, rate limits, error conditions, or what 'update the deployment' entails operationally. The Returns section mentions a response dictionary but gives no details about success/failure indicators or structure. This is inadequate for a mutation tool with zero annotation coverage.

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

Conciseness3/5

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

The description is structured with Args, Example Usage, and Returns sections, which is good organization. However, the example is overly long (25+ lines) with embedded comments and syntax issues, making it inefficient. The core purpose statement is clear but could be more front-loaded. Some sentences like 'Add these if any additional detectors than that in the policy are needed' are instructional rather than descriptive.

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 mutation tool with 2 parameters (one being a complex nested object), 0% schema description coverage, no annotations, and no output schema, the description is incomplete. While it shows an example configuration, it doesn't explain the full behavioral context: what fields are modifiable, validation rules, side effects, error handling, or response format. The Returns section is vague ('A dictionary containing...') without structural details.

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 names both parameters ('deployment_name' and 'new_deployment_config') and provides an extensive example showing a complex nested configuration object with guardrails policies. However, the example contains syntax errors (e.g., 'sample_deployment_config =' inside JSON) and doesn't clearly map to the actual parameter structure. It adds some semantic value but doesn't fully document the parameter expectations beyond the basic names.

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: 'Modify the deployment configuration and update the deployment.' This specifies the verb ('modify' and 'update') and resource ('deployment configuration' and 'deployment'), making it clear this is a mutation operation. However, it doesn't explicitly differentiate from sibling tools like 'modify_model_config' or 'update_guardrails_policy' that might handle similar configuration changes.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'add_deployment', 'get_deployment_details', 'list_deployments', and 'remove_deployment', there's no indication of prerequisites (e.g., deployment must exist), when to choose modification over recreation, or what happens if the deployment doesn't exist. The example shows complex configuration but doesn't explain usage context.

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