Skip to main content
Glama
Sign In
OCI MCP Server

OCI MCP Server

by sarthak-pansare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

instance_action

Start, stop, soft-stop, reset, or soft-reset an OCI compute instance by specifying its ID and desired action.

Instructions

Power action. action: START|STOP|SOFTSTOP|RESET|SOFTRESET.

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>",
      "action": "<action>"
    },
    "name": "instance_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYes
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior1/5

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

No annotations provided, and the description fails to disclose behavioral traits such as idempotency, side effects, permissions required, or asynchronous nature. For a power action tool, this is a critical gap.

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

Conciseness3/5

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

The description is very short (one line), which is concise, but the phrasing 'Power action' is somewhat ambiguous. It front-loads the concept but lacks clarity.

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?

No output schema, no annotations, and minimal parameter details. The description does not explain return values, success/failure conditions, or execution model, making it incomplete for agent decision-making.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate. While it lists allowed values for 'action', it does not explain the instance_id parameter or the effects of each action. It adds some value but is insufficient for full 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?

Description states 'Power action' and enumerates specific actions (START|STOP|SOFTSTOP|RESET|SOFTRESET), making the purpose clear. It distinguishes from sibling tools like launch_instance and terminate_instance by focusing on power state operations.

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. The description does not mention prerequisites, context, or exclusions, leaving the agent to infer usage from the action list.

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