Skip to main content
Glama
jkmills

Nutanix MCP Server

by jkmills

get_category

Retrieve all values for a specific category key using its UUID. For example, get environment values such as Production, Dev, or Test.

Instructions

Get all values for a specific category key. Example: category 'Environment' may have values 'Production', 'Dev', 'Test'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_uuidYesThe UUID (extId) of the category

Implementation Reference

  • The handler function for 'get_category'. Calls v4 API to get category details by UUID via the prism config/categories endpoint.
    async def handle_get_category(
        client: NutanixClient, arguments: dict[str, Any]
    ) -> dict[str, Any]:
        """Get category details using v4 prism API."""
        category_uuid = arguments["category_uuid"]
        result = await client.v4_get(
            namespace="prism",
            path=f"config/categories/{category_uuid}",
        )
        return result.get("data", result)
  • Input schema definition for 'get_category' tool. Requires 'category_uuid' (string) as the sole input.
        {
            "name": "get_category",
            "description": (
                "Get all values for a specific category key. "
                "Example: category 'Environment' may have values 'Production', 'Dev', 'Test'."
            ),
            "inputSchema": {
                "type": "object",
                "properties": {
                    "category_uuid": {
                        "type": "string",
                        "description": "The UUID (extId) of the category",
                    },
                },
                "required": ["category_uuid"],
            },
        },
    ]
  • Registration of 'get_category' in the NETWORKING_HANDLERS dispatch table, mapping the name to handle_get_category.
    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,
    }
  • get_all_tools() aggregates NETWORKING_TOOLS (which includes get_category) into the global tool list.
    def get_all_tools() -> list[dict]:
        """Return all registered tool definitions."""
        return VM_TOOLS + CLUSTER_TOOLS + PE_TOOLS + REPORT_TOOLS + NETWORKING_TOOLS
  • ALL_HANDLERS dictionary merges NETWORKING_HANDLERS, enabling the server to route 'get_category' calls to handle_get_category.
    # Merge all handler dispatch tables
    ALL_HANDLERS: dict[str, Any] = {
        **VM_HANDLERS,
        **CLUSTER_HANDLERS,
        **PE_HANDLERS,
        **REPORT_HANDLERS,
        **NETWORKING_HANDLERS,
    }
Behavior2/5

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

No annotations provided. Description implies a read operation but does not explicitly state safe, idempotent behavior. Lacks details on side effects, permissions, or output limits.

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?

Two concise sentences with an example. No wasted words, front-loaded primary action.

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?

Simple tool, but description lacks details on output format (list of strings/objects) and when to use. No output schema, so description should specify return type.

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 has 100% coverage with description of category_uuid. Description adds an example but does not significantly enhance understanding beyond schema. Baseline 3 is appropriate.

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?

Clearly states action: 'Get all values for a specific category key.' Distinct from sibling tools which focus on VMs, clusters, hosts, etc. Example with 'Environment' adds clarity.

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?

No guidance on when to use this over sibling tools like list_categories. The example is helpful but does not specify context or prerequisites.

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