Skip to main content
Glama

category_create

Create a category key/value pair in Nutanix Prism Central to organize resources with custom labels such as Environment or Production.

Instructions

[WRITE][risk=medium] Create a category key/value pair.

Args:
    key: Category key (e.g. "Environment").
    value: Category value (e.g. "Production").
    description: Optional human-readable description.
    target: Prism Central target name from config; omit for the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
valueYes
targetNo
descriptionNo
Behavior3/5

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

The description includes a [WRITE][risk=medium] tag, indicating it mutates state and has medium risk, which adds transparency beyond the tool name. However, it does not detail error handling, idempotency, or authorization requirements.

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?

The description is concise, front-loading the purpose and risk, then listing parameters in a clear format. Every sentence is informative without redundancy.

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?

While the description covers parameters well, it omits the return value or response structure. Given no output schema, this gap reduces completeness for agent decision-making.

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 compensates fully by explaining each parameter's meaning and providing examples, adding significant value over the schema alone.

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 clearly states the tool creates a category key/value pair, using a specific verb and resource. This distinguishes it from sibling tools like category_list and category_assign.

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 usage for creating new categories but does not explicitly state when to use this tool versus alternatives like category_assign. Lacks exclusions or when-not-to-use guidance.

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/AIops-tools/Nutanix-AIops'

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