delete_cluster
Delete an OKE cluster by providing its cluster ID to terminate and clean up resources.
Instructions
Delete an OKE cluster.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cluster_id | Yes |
Delete an OKE cluster by providing its cluster ID to terminate and clean up resources.
Delete an OKE cluster.
| Name | Required | Description | Default |
|---|---|---|---|
| cluster_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description only says 'Delete an OKE cluster,' omitting details on destructive behavior, permission requirements, or consequences. The tool is clearly a deletion, but lacks transparency beyond that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise at four words, but this brevity sacrifices useful detail. It is front-loaded but not informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive tool, the description fails to explain post-deletion state, dependencies, or interaction with other resources. Lacks necessary completeness for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% description coverage for the only parameter 'cluster_id', and the description adds no explanation of what the parameter expects (e.g., OCID, name, format).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Delete' and the resource 'OKE cluster', making it unambiguous and distinct from sibling tools like create_cluster or list_clusters.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, no prerequisites or context (e.g., cluster must exist, potential cascading deletes).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sarthak-pansare/oci-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server