Skip to main content
Glama

get_boot_volume

Retrieve detailed boot volume information including size, performance metrics, and source image data from Oracle Cloud Infrastructure using the boot volume OCID.

Instructions

Get detailed information about a specific boot volume.

Args:
    boot_volume_id: OCID of the boot volume to retrieve

Returns:
    Detailed boot volume information including size, performance, and source image

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boot_volume_idYes

Implementation Reference

  • Core handler function implementing the logic to retrieve boot volume details using OCI BlockstorageClient.get_boot_volume and formatting the response.
    def get_boot_volume(block_storage_client: oci.core.BlockstorageClient, boot_volume_id: str) -> Dict[str, Any]:
        """
        Get details of a specific boot volume.
        
        Args:
            block_storage_client: OCI BlockStorage client
            boot_volume_id: OCID of the boot volume
            
        Returns:
            Details of the boot volume
        """
        try:
            boot_volume = block_storage_client.get_boot_volume(boot_volume_id).data
            
            boot_volume_details = {
                "id": boot_volume.id,
                "display_name": boot_volume.display_name,
                "compartment_id": boot_volume.compartment_id,
                "availability_domain": boot_volume.availability_domain,
                "size_in_mbs": boot_volume.size_in_mbs,
                "size_in_gbs": boot_volume.size_in_gbs,
                "lifecycle_state": boot_volume.lifecycle_state,
                "time_created": str(boot_volume.time_created),
                "is_hydrated": boot_volume.is_hydrated,
                "vpus_per_gb": boot_volume.vpus_per_gb,
                "is_auto_tune_enabled": boot_volume.is_auto_tune_enabled,
                "auto_tuned_vpus_per_gb": boot_volume.auto_tuned_vpus_per_gb,
                "kms_key_id": boot_volume.kms_key_id,
                "source_details": {
                    "type": boot_volume.source_details.type if boot_volume.source_details else None,
                    "id": boot_volume.source_details.id if boot_volume.source_details else None,
                } if boot_volume.source_details else None,
            }
            
            logger.info(f"Retrieved details for boot volume {boot_volume_id}")
            return boot_volume_details
            
        except Exception as e:
            logger.exception(f"Error getting boot volume details: {e}")
            raise
  • MCP tool registration using @mcp.tool(name='get_boot_volume'), including wrapper decorator for logging/error handling and docstring schema, which delegates to the core handler.
    @mcp.tool(name="get_boot_volume")
    @mcp_tool_wrapper(
        start_msg="Getting boot volume details for {boot_volume_id}...",
        success_msg="Retrieved boot volume details successfully",
        error_prefix="Error getting boot volume details"
    )
    async def mcp_get_boot_volume(ctx: Context, boot_volume_id: str) -> Dict[str, Any]:
        """
        Get detailed information about a specific boot volume.
    
        Args:
            boot_volume_id: OCID of the boot volume to retrieve
    
        Returns:
            Detailed boot volume information including size, performance, and source image
        """
        return get_boot_volume(oci_clients["block_storage"], boot_volume_id)
  • Docstring providing input schema (boot_volume_id parameter) and output description for the MCP tool.
    """
    Get detailed information about a specific boot volume.
    
    Args:
        boot_volume_id: OCID of the boot volume to retrieve
    
    Returns:
        Detailed boot volume information including size, performance, and source image
    """
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), implying it's non-destructive, but doesn't cover critical aspects like authentication requirements, rate limits, error conditions, or response format details. The description adds minimal behavioral context beyond the basic action.

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

Conciseness5/5

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

The description is well-structured and appropriately sized. It starts with a clear purpose statement, followed by 'Args' and 'Returns' sections that efficiently document inputs and outputs. Every sentence adds value without redundancy, making it easy to parse and understand quickly.

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

Completeness3/5

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

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is adequate but has gaps. It explains the parameter and return value at a high level, but lacks details on authentication, error handling, or performance characteristics. For a simple read tool, it meets minimum viability but could be more comprehensive.

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

Parameters4/5

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

The description adds meaningful semantics for the single parameter: 'boot_volume_id: OCID of the boot volume to retrieve.' This clarifies that the ID is an OCID (Oracle Cloud Identifier) and specifies its purpose. With schema description coverage at 0% (no schema descriptions), the description fully compensates by providing essential parameter context, though it doesn't cover format or validation rules.

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 tool's purpose: 'Get detailed information about a specific boot volume.' It specifies the verb ('Get') and resource ('boot volume'), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'get_volume' or 'list_boot_volumes', which would require a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'list_boot_volumes' for listing volumes or 'get_volume' for other volume types, nor does it specify prerequisites or contexts for usage, leaving the agent without explicit selection criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jopsis/mcp-server-oci'

If you have feedback or need assistance with the MCP directory API, please join our Discord server