OCI MCP Server

list_node_pools

Retrieve a list of Oracle Kubernetes Engine (OKE) node pools in a compartment, with optional filtering by cluster and limit.

Instructions

List OKE node pools.

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": {
      "compartment_id": "<compartment_id>"
    },
    "name": "list_node_pools"
  }
}

Input Schema

Name	Required	Description	Default
`compartment_id`	Yes
`cluster_id`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 30, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It merely states the verb and resource without indicating whether the operation is read-only, whether pagination is handled, or any side effects.

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

Conciseness4/5

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

The description is a single, concise sentence with no wasted words. It is appropriately front-loaded but could benefit from slight expansion to improve other dimensions.

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 the absence of an output schema and annotations, the description should explain what the response contains and any notable behaviors. It falls short, leaving the agent without critical context about pagination, return fields, or error handling.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the description must clarify parameter meanings. However, it adds zero information about compartment_id, cluster_id, or limit beyond what their names imply. The schema already provides basic names, so the description offers no added value.

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

Purpose4/5

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

The description clearly states the action ('List') and resource ('OKE node pools'), making it unambiguous. It is specific enough to distinguish from sibling tools that list other resources, but lacks additional context about the scope or filtering.

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 is provided on when to use this tool versus alternatives, such as list_clusters or other list operations. It does not mention prerequisites, permissions, or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server