List OKE clusters in Oracle Cloud Infrastructure, filtered by compartment ID and limited to a specified number.
List OKE clusters.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_clusters"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| compartment_id | No | ||
| limit | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It only says 'List OKE clusters' without disclosing that it is read-only, any required permissions, pagination behavior, or whether it lists clusters across all compartments. The parameters imply some filtering but this is not explained.
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?
The description is a single sentence, which is concise, but it is under-specified. It lacks necessary details to be considered appropriately sized; conciseness should not come at the cost of completeness.
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?
Given the tool has two parameters, no output schema, and no annotations, the description is too brief. It does not explain the return format, pagination, or the scope of clusters listed. For a complete context, it should at least mention default behavior and parameter effects.
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?
Schema description coverage is 0%, yet the description does not mention any parameters. It does not explain that compartment_id filters by compartment or that limit controls the maximum number of results. The agent receives no guidance on how to use the two parameters.
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 states 'List OKE clusters', clearly identifying the verb and resource. However, it does not differentiate from sibling tools like list_node_pools or get_cluster, which are also list/get tools for related resources.
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. For example, when to list clusters versus using get_cluster for a specific cluster or list_node_pools for node pools. Missing context about filtering or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.