Skip to main content
Glama

get_file_system

Retrieve detailed information about an Oracle Cloud Infrastructure File Storage file system, including metered bytes and snapshots, by providing its OCID.

Instructions

Get detailed information about a specific File Storage file system.

Args:
    file_system_id: OCID of the file system to retrieve

Returns:
    Detailed file system information including metered bytes and snapshots

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_system_idYes

Implementation Reference

  • MCP tool handler function 'mcp_get_file_system' that implements the 'get_file_system' tool logic by calling the helper function with the file storage client and file_system_id.
    @mcp.tool(name="get_file_system")
    @mcp_tool_wrapper(
        start_msg="Getting file system details for {file_system_id}...",
        success_msg="Retrieved file system details successfully",
        error_prefix="Error getting file system details"
    )
    async def mcp_get_file_system(ctx: Context, file_system_id: str) -> Dict[str, Any]:
        """
        Get detailed information about a specific File Storage file system.
    
        Args:
            file_system_id: OCID of the file system to retrieve
    
        Returns:
            Detailed file system information including metered bytes and snapshots
        """
        return get_file_system(oci_clients["file_storage"], file_system_id)
  • Helper function that performs the actual OCI API call to retrieve file system details using the FileStorageClient.
    def get_file_system(file_storage_client: oci.file_storage.FileStorageClient, file_system_id: str) -> Dict[str, Any]:
        """
        Get details of a specific file system.
        
        Args:
            file_storage_client: OCI FileStorage client
            file_system_id: OCID of the file system
            
        Returns:
            Details of the file system
        """
        try:
            file_system = file_storage_client.get_file_system(file_system_id).data
            
            file_system_details = {
                "id": file_system.id,
                "display_name": file_system.display_name,
                "compartment_id": file_system.compartment_id,
                "availability_domain": file_system.availability_domain,
                "lifecycle_state": file_system.lifecycle_state,
                "time_created": str(file_system.time_created),
                "metered_bytes": file_system.metered_bytes,
                "is_clone_parent": file_system.is_clone_parent,
                "is_hydrated": file_system.is_hydrated,
                "lifecycle_details": file_system.lifecycle_details,
                "kms_key_id": file_system.kms_key_id,
                "source_details": {
                    "parent_file_system_id": file_system.source_details.parent_file_system_id if file_system.source_details else None,
                    "source_snapshot_id": file_system.source_details.source_snapshot_id if file_system.source_details else None,
                } if file_system.source_details else None,
            }
            
            logger.info(f"Retrieved details for file system {file_system_id}")
            return file_system_details
            
        except Exception as e:
            logger.exception(f"Error getting file system details: {e}")
            raise
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves detailed information, implying a read-only operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or whether it's idempotent. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 front-loaded with the core purpose, followed by clear sections for Args and Returns. Every sentence earns its place without redundancy, making it efficient and easy to parse.

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 no annotations, no output schema, and low schema coverage, the description provides basic purpose and parameter semantics but lacks details on return format, error handling, or operational context. It's minimally adequate for a simple retrieval tool but doesn't fully address the gaps left by missing structured data.

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 explicitly documents the single parameter 'file_system_id' with its purpose ('OCID of the file system to retrieve'), adding meaningful context beyond the schema's minimal title. With 0% schema description coverage and only one parameter, this effectively compensates, though it could specify OCID format or constraints.

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 verb ('Get detailed information') and resource ('a specific File Storage file system'), making the purpose unambiguous. It distinguishes from sibling 'list_file_systems' by specifying retrieval of a single item rather than listing multiple. However, it doesn't explicitly contrast with other get_* tools beyond the resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when detailed information about a specific file system is needed, contrasting with 'list_file_systems' for listing. However, it doesn't provide explicit when-to-use guidance, prerequisites, or mention alternatives for similar retrieval operations among other get_* tools.

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