Skip to main content
Glama
enkryptai

Enkrypt AI MCP Server

Official
by enkryptai

modify_model_config

Adjust and update model configurations for AI models, including parameters like version, provider, and API details, to ensure accurate and optimized performance.

Instructions

Modify the model configuration and update the model.

Args: new_model_config: The sample model configuration to be modified. Example usage: { "model_saved_name": "example_model_name", # The name under which the model is saved. "testing_for": "LLM", # The purpose for which the model is being tested. (Always LLM) "model_name": "example_model", # The name of the model. (e.g., gpt-4o, claude-3-5-sonnet, etc.) "modality": "text", # The type of data the model works with (e.g., text, image). "model_config": { "model_version": "1.0", # The version of the model. "model_provider": "example_provider", # The provider of the model. (e.g., openai, anthropic, etc.) "endpoint_url": "https://api.example.com/model", # The endpoint URL for the model. "apikey": "example_api_key", # The API key to access the model. }, } test_model_saved_name: The saved name of the model to be tested.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
new_model_configYes
test_model_saved_nameYes

Implementation Reference

  • Handler function for the 'modify_model_config' tool. Decorated with @mcp.tool() for registration. Modifies a model's configuration using the model_client and returns the response as a dictionary.
    def modify_model_config(new_model_config: Dict[str, Any], test_model_saved_name: str) -> Dict[str, Any]:
        """
        Modify the model configuration and update the model.
    
        Args:
            new_model_config: The sample model configuration to be modified.
                Example usage:
                    {
                        "model_saved_name": "example_model_name",  # The name under which the model is saved.
                        "testing_for": "LLM",  # The purpose for which the model is being tested. (Always LLM)
                        "model_name": "example_model",  # The name of the model. (e.g., gpt-4o, claude-3-5-sonnet, etc.)
                        "modality": "text",  # The type of data the model works with (e.g., text, image).
                        "model_config": {
                            "model_version": "1.0",  # The version of the model.
                            "model_provider": "example_provider",  # The provider of the model. (e.g., openai, anthropic, etc.)
                            "endpoint_url": "https://api.example.com/model",  # The endpoint URL for the model. 
                            "apikey": "example_api_key",  # The API key to access the model.
                        },
                    }
            test_model_saved_name: The saved name of the model to be tested.
    
        Returns:
            A dictionary containing the response message and details of the modified model.
        """
        # Modify model configuration
    
        # Update the model_saved_name if needed
        # new_model_config["model_saved_name"] = "New Model Name"
    
        old_model_saved_name = None
        if new_model_config["model_saved_name"] != test_model_saved_name:
            old_model_saved_name = test_model_saved_name
    
        modify_response = model_client.modify_model(old_model_saved_name=old_model_saved_name, config=new_model_config)
    
        # Print as a dictionary
        return modify_response.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 for behavioral disclosure. While it states the tool modifies and updates a model, it doesn't describe important behavioral aspects: whether this requires special permissions, if changes are reversible, what happens to existing configurations not mentioned, or potential side effects. The example shows authentication details (apikey), suggesting this might involve privileged operations, but this isn't explicitly stated.

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 front-loaded with the core purpose, but the extensive example occupies significant space. While the example is valuable for parameter clarification, it makes the description quite long. The structure with Args/Returns sections is clear, but some information in the example (like 'Always LLM') could potentially be moved to parameter documentation.

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?

For a mutation tool with no annotations and no output schema, the description provides good parameter documentation but lacks important context. It doesn't explain what 'update the model' means operationally, what the return dictionary contains, or potential error conditions. The example helps but doesn't fully compensate for the missing behavioral and output context.

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, the description fully compensates by providing detailed parameter semantics. It explains both parameters thoroughly: 'new_model_config' gets an extensive example with field-by-field documentation, and 'test_model_saved_name' is clearly defined as 'The saved name of the model to be tested.' This goes well beyond what the bare schema provides.

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 model configuration and update the model.' This specifies both the action (modify/update) and the resource (model configuration/model). However, it doesn't explicitly differentiate from sibling tools like 'modify_deployment_config' or 'update_guardrails_policy', which prevents a perfect score.

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 sibling tools like 'add_model', 'get_model_details', 'list_models', and 'remove_model' available, there's no indication of when this modification tool is appropriate versus creating a new model or retrieving existing details.

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