Nutanix MCP Server

Overview Schema Source Related Servers Discussions Admin

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'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category_uuid": "<category_uuid>"
    },
    "name": "get_category"
  }
}

Input Schema

Name	Required	Description	Default
`category_uuid`	Yes	The UUID (extId) of the category

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 7, 2026

TDQS

B3.2/5.0

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.