Skip to main content
Glama
Sign In
OCI MCP Server

OCI MCP Server

by sarthak-pansare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

terminate_instance

Terminate an OCI compute instance. Optionally preserve the boot volume for data retention.

Instructions

Terminate an instance.

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": {
      "instance_id": "<instance_id>"
    },
    "name": "terminate_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYes
preserve_boot_volumeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

The description lacks behavioral details beyond the action itself. No annotations are provided, so the description should convey what the termination entails (e.g., irreversibility, impact on attached volumes). The parameter 'preserve_boot_volume' hints at optional behavior, but the description does not explain it.

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

Conciseness2/5

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

While only one sentence long, the description is too terse and sacrifices necessary detail. Conciseness should not come at the expense of clarity; the current version is under-specified for safe and correct use.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a termination operation (irreversible, potential data loss), the description is severely incomplete. It lacks any explanation of consequences, prerequisites, or post-conditions. The absence of annotations and output schema further exacerbates the gap.

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

Parameters1/5

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

The schema has 0% description coverage, and the description adds nothing about the parameters. It does not explain the meaning of 'instance_id' (e.g., format or type) or the effect of 'preserve_boot_volume' (e.g., whether it retains the boot volume). This leaves the agent with no additional semantic understanding.

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 'Terminate an instance' clearly states the action (terminate) and the resource (instance), distinguishing it from siblings like 'launch_instance' or 'list_instances'. However, it does not specify the type of instance (e.g., compute instance) or the cloud provider, relying on context.

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 tool versus alternatives. It does not mention prerequisites (e.g., instance must be running) or situations where termination is appropriate vs. other actions like 'instance_action' for stopping.

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

Deploy Server

Other Tools