Skip to main content
Glama
jkmills

Nutanix MCP Server

by jkmills

get_image

Retrieve detailed information about a specific disk image including size, type, source, and cluster placement by providing its UUID.

Instructions

Get detailed information about a specific disk image by UUID. Returns size, type, source, and cluster placement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_uuidYesThe UUID (extId) of the image

Implementation Reference

  • The `handle_get_image` async function that executes the get_image tool logic. It takes a NutanixClient and arguments dict, extracts `image_uuid`, calls `client.v4_get(namespace='vmm', path=f'content/images/{image_uuid}')`, and returns the result data.
    async def handle_get_image(
        client: NutanixClient, arguments: dict[str, Any]
    ) -> dict[str, Any]:
        """Get image details using v4 vmm API."""
        image_uuid = arguments["image_uuid"]
        result = await client.v4_get(
            namespace="vmm",
            path=f"content/images/{image_uuid}",
        )
        return result.get("data", result)
  • Input schema definition for the get_image tool. Defines the `image_uuid` string parameter as required, with description explaining its purpose.
    {
        "name": "get_image",
        "description": (
            "Get detailed information about a specific disk image by UUID. "
            "Returns size, type, source, and cluster placement."
        ),
        "inputSchema": {
            "type": "object",
            "properties": {
                "image_uuid": {
                    "type": "string",
                    "description": "The UUID (extId) of the image",
                },
            },
            "required": ["image_uuid"],
        },
  • The `NETWORKING_HANDLERS` dispatch table mapping the string 'get_image' to the `handle_get_image` function, used by the server's call_tool handler.
    NETWORKING_HANDLERS: dict[str, Any] = {
        "list_subnets": handle_list_subnets,
        "get_subnet": handle_get_subnet,
        "list_images": handle_list_images,
        "get_image": handle_get_image,
        "list_categories": handle_list_categories,
        "get_category": handle_get_category,
    }
  • The `get_all_tools()` function that aggregates tool definitions including NETWORKING_TOOLS (which contains the get_image definition).
    def get_all_tools() -> list[dict]:
        """Return all registered tool definitions."""
        return VM_TOOLS + CLUSTER_TOOLS + PE_TOOLS + REPORT_TOOLS + NETWORKING_TOOLS
  • The `ALL_HANDLERS` dictionary in server.py that merges all handler dispatch tables, including NETWORKING_HANDLERS which contains the get_image handler.
    # Merge all handler dispatch tables
    ALL_HANDLERS: dict[str, Any] = {
        **VM_HANDLERS,
        **CLUSTER_HANDLERS,
        **PE_HANDLERS,
        **REPORT_HANDLERS,
        **NETWORKING_HANDLERS,
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It states return fields but does not disclose read-only nature, authentication, or error behavior. Adequate but not thorough.

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

Conciseness5/5

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

Single sentence, front-loaded with action, no wasted words. Perfectly concise for the tool's simplicity.

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?

For a simple get operation with one parameter and no output schema, the description adequately covers purpose, input, and return fields. Minor gap: no mention of error handling, but acceptable.

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 already describes 'image_uuid' as 'The UUID (extId) of the image'. The description adds 'By UUID' and return fields, but with 100% schema coverage, the description adds minimal extra meaning.

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

Purpose5/5

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

The description uses specific verb ('Get') and resource ('detailed information about a specific disk image by UUID'), clearly differentiating from sibling tools like 'list_images' or other 'get_*' tools.

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 implies use when needing details for a known UUID, contrasting with listing all images, but provides no explicit when-to-use or when-not-to-use guidance and no alternatives mentioned.

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

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/jkmills/nutanix-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server