Skip to main content
Glama
enkryptai

Enkrypt AI MCP Server

Official
by enkryptai

add_agent

Configure and deploy a new AI agent within Enkrypt AI MCP Server. Specify agent details, endpoint URL, custom headers, response format, and tools to integrate the agent for real-time AI safety analysis and prompt auditing.

Instructions

Add a new agent using the provided configuration.

Args: config: A dictionary containing the agent configuration details. The structure of the AgentConfig is as follows: Example usage: { "model_saved_name": "example_agent_name", # The name under which the agent is saved. "model_version": "v1", # The version of the agent. "testing_for": "agents", # The purpose for which the agent is being tested. (Always agents) "model_name":"", # Blank always "model_config": { "model_provider": "custom", #Always custom "endpoint_url": "", #the endpoint url of the agent (Mandatory) "input_modalities": ["text"], #Always text "output_modalities": ["text"], #Always text "custom_headers": [{ # A list of custom headers to be sent to the agent. (Mandatory) "key": "Content-Type", "value": "application/json" }...], "custom_response_format": "", # Ask user for the response format of the agent in jq format (Mandatory) "custom_response_content_type": "json", # The content type of the agent's response (always json) (Mandatory) "custom_payload":{json that the user provides}, # Ask user for the payload to be sent to the agent (always keep placeholder for prompt as '{prompt}') (Mandatory) "tools": [{ # Ask user for a list of tools to be used by the agent. (MANDATORY) "name": "name of the tool", "description": "description of the tool" }...] }, } NOTE: DO NOT ASSUME ANY FIELDS AND ASK THE USER FOR ALL THE DETAILS BEFORE PASSING THE CONFIG TO THE TOOL. Ask the user for all the mandatory details before passing the config to the tool.

Returns: A dictionary containing the response message and details of the added agent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYes

Implementation Reference

  • The handler function for the 'add_agent' tool. Decorated with @mcp.tool() for registration in MCP. Takes agent configuration, calls model_client.add_model, and returns the response as a dictionary. Includes detailed docstring describing input schema.
    @mcp.tool()
    def add_agent(config: Dict[str, Any]) -> Dict[str, Any]:
        """
        Add a new agent using the provided configuration.
    
        Args:
            config: A dictionary containing the agent configuration details. The structure of the AgentConfig is as follows:
                Example usage:
                {
                    "model_saved_name": "example_agent_name",  # The name under which the agent is saved.
                    "model_version": "v1",  # The version of the agent.
                    "testing_for": "agents", # The purpose for which the agent is being tested. (Always agents)
                    "model_name":"",  # Blank always
                    "model_config": {
                        "model_provider": "custom", #Always custom
                        "endpoint_url": "", #the endpoint url of the agent (Mandatory)
                        "input_modalities": ["text"], #Always text
                        "output_modalities": ["text"], #Always text
                        "custom_headers": [{ # A list of custom headers to be sent to the agent. (Mandatory)
                            "key": "Content-Type",
                            "value": "application/json"
                        }...],
                        "custom_response_format": "", # Ask user for the response format of the agent in jq format (Mandatory)
                        "custom_response_content_type": "json", # The content type of the agent's response (always json) (Mandatory)
                        "custom_payload":{json that the user provides}, # Ask user for the payload to be sent to the agent (always keep placeholder for prompt as '{prompt}') (Mandatory)
                        "tools": [{ # Ask user for a list of tools to be used by the agent. (MANDATORY)
                                "name": "name of the tool",
                                "description": "description of the tool"
                                }...]
                    },
                }
        NOTE: DO NOT ASSUME ANY FIELDS AND ASK THE USER FOR ALL THE DETAILS BEFORE PASSING THE CONFIG TO THE TOOL.
        Ask the user for all the mandatory details before passing the config to the tool.
    
        Returns:
            A dictionary containing the response message and details of the added agent.
        """
        # Add the agent using the provided configuration
        add_agent_response = model_client.add_model(config=copy.deepcopy(config))
        
        # Return the response as a dictionary
        return add_agent_response.to_dict()
  • The docstring of the add_agent function provides the detailed input schema, example configuration structure, mandatory fields, and notes on usage.
    """
    Add a new agent using the provided configuration.
    
    Args:
        config: A dictionary containing the agent configuration details. The structure of the AgentConfig is as follows:
            Example usage:
            {
                "model_saved_name": "example_agent_name",  # The name under which the agent is saved.
                "model_version": "v1",  # The version of the agent.
                "testing_for": "agents", # The purpose for which the agent is being tested. (Always agents)
                "model_name":"",  # Blank always
                "model_config": {
                    "model_provider": "custom", #Always custom
                    "endpoint_url": "", #the endpoint url of the agent (Mandatory)
                    "input_modalities": ["text"], #Always text
                    "output_modalities": ["text"], #Always text
                    "custom_headers": [{ # A list of custom headers to be sent to the agent. (Mandatory)
                        "key": "Content-Type",
                        "value": "application/json"
                    }...],
                    "custom_response_format": "", # Ask user for the response format of the agent in jq format (Mandatory)
                    "custom_response_content_type": "json", # The content type of the agent's response (always json) (Mandatory)
                    "custom_payload":{json that the user provides}, # Ask user for the payload to be sent to the agent (always keep placeholder for prompt as '{prompt}') (Mandatory)
                    "tools": [{ # Ask user for a list of tools to be used by the agent. (MANDATORY)
                            "name": "name of the tool",
                            "description": "description of the tool"
                            }...]
                },
            }
    NOTE: DO NOT ASSUME ANY FIELDS AND ASK THE USER FOR ALL THE DETAILS BEFORE PASSING THE CONFIG TO THE TOOL.
    Ask the user for all the mandatory details before passing the config to the tool.
    
    Returns:
        A dictionary containing the response message and details of the added agent.
    """
  • The @mcp.tool() decorator registers the add_agent 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 it mentions that the tool 'Adds a new agent' (implying a write/mutation operation), it doesn't address critical behavioral aspects: whether this requires specific permissions, what happens on failure, whether the agent becomes immediately active, or if there are rate limits. The example config provides some implementation details but lacks operational context.

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 appropriately front-loaded with the core purpose, but the extensive example and implementation notes create significant length. While the content is valuable given the complex parameter, some information (like repeated 'Mandatory' labels and implementation directives) could be more efficiently structured. The 'NOTE' section feels like implementation guidance rather than pure tool description.

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 complex nested parameter structure (1 parameter with deep nesting, 0% schema coverage, no output schema), the description provides substantial context. It thoroughly documents the config parameter's structure, includes an example with field semantics, and specifies mandatory requirements. The main gap is lack of output information (only mentions 'A dictionary containing the response message and details' without structure), but this is partially mitigated by the detailed input documentation.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and a single complex parameter ('config'), the description provides extensive semantic information that completely compensates for the schema gap. It details the nested structure of AgentConfig, provides a comprehensive example with field explanations, specifies mandatory versus optional fields, and includes implementation notes about placeholder usage and required user input collection.

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 agent using the provided configuration.' It specifies the verb ('Add') and resource ('agent'), making the function unambiguous. However, it doesn't explicitly differentiate this from sibling tools like 'add_model' or 'add_deployment', which appear to be related creation operations.

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. While it mentions 'DO NOT ASSUME ANY FIELDS AND ASK THE USER FOR ALL THE DETAILS,' this is about parameter collection rather than tool selection. There's no indication of prerequisites, when this tool is appropriate versus other 'add_' tools, or what scenarios warrant its use.

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