Skip to main content
Glama
enesjakozh
enkryptai

Enkrypt AI MCP Server

Official
by enkryptai
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

list_deployments

Retrieve and display details of all deployments, starting with the first one. Provides a dictionary listing deployment information for Enkrypt AI MCP Server integration.

Instructions

List all deployments and print details of the first deployment.

Returns: A dictionary containing the list of deployments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp_server.py:899-910 (handler)
    The core handler function for the 'list_deployments' MCP tool. It is decorated with @mcp.tool() for registration and execution. The function calls deployment_client.list_deployments() and returns the result as a dictionary.
    def list_deployments() -> Dict[str, Any]:
    """
    List all deployments and print details of the first deployment.

    Returns:
        A dictionary containing the list of deployments.
    """
    # List all deployments
    deployments = deployment_client.list_deployments()

    # Return the list of deployments as a dictionary
    return deployments.to_dict()

Tool Definition Quality

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the tool lists all deployments and prints details of the first, but does not disclose behavioral traits such as pagination, rate limits, permissions required, or what 'print details' entails. This leaves significant gaps for a tool that likely interacts with deployments.

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 concise with two sentences, but the second sentence about printing details of the first deployment adds potential confusion without clear value. It could be more front-loaded by focusing solely on the listing function. Some waste is present.

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 no annotations, no output schema, and a list operation with potential complexity (e.g., multiple deployments), the description is incomplete. It does not explain the return format beyond 'a dictionary containing the list of deployments,' missing details like structure, keys, or error handling. More context is needed for effective use.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description does not add parameter details, which is appropriate. Baseline is 4 for 0 parameters, as the schema fully covers the absence of inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'List all deployments and print details of the first deployment,' which provides a clear verb ('List') and resource ('deployments'). However, it does not differentiate from sibling tools like 'get_deployment_details' or explain how it differs from other listing tools (e.g., 'list_models'). The purpose is clear but lacks sibling distinction.

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. It does not mention when to use 'list_deployments' over 'get_deployment_details' or other sibling tools, nor does it specify any prerequisites or exclusions. Usage is implied but not explicit.

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