Skip to main content
Glama

list_groups

Retrieve all IAM groups within a specified Oracle Cloud compartment, including member counts and status details for access management.

Instructions

List all IAM groups in a compartment.

Args:
    compartment_id: OCID of the compartment to list groups from

Returns:
    List of groups with their members count and state

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
compartment_idYes

Implementation Reference

  • MCP tool registration and handler for 'list_groups'. This async function is decorated with @mcp.tool(name='list_groups') and wraps the core list_groups implementation, handling context, errors, and OCI client access.
    @mcp.tool(name="list_groups")
    @mcp_tool_wrapper(
        start_msg="Listing IAM groups in compartment {compartment_id}...",
        error_prefix="Error listing groups"
    )
    async def mcp_list_groups(ctx: Context, compartment_id: str) -> List[Dict[str, Any]]:
        """
        List all IAM groups in a compartment.
    
        Args:
            compartment_id: OCID of the compartment to list groups from
    
        Returns:
            List of groups with their members count and state
        """
        return list_groups(oci_clients["identity"], compartment_id)
  • Core helper function implementing the logic to list OCI Identity groups using the OCI SDK, formatting results into a list of dictionaries.
    def list_groups(identity_client: oci.identity.IdentityClient, compartment_id: str) -> List[Dict[str, Any]]:
        """
        List all groups in a compartment.
        
        Args:
            identity_client: OCI Identity client
            compartment_id: OCID of the compartment
            
        Returns:
            List of groups with their details
        """
        try:
            groups_response = oci.pagination.list_call_get_all_results(
                identity_client.list_groups,
                compartment_id
            )
            
            groups = []
            for group in groups_response.data:
                groups.append({
                    "id": group.id,
                    "name": group.name,
                    "description": group.description,
                    "lifecycle_state": group.lifecycle_state,
                    "time_created": str(group.time_created),
                    "compartment_id": group.compartment_id,
                })
            
            logger.info(f"Found {len(groups)} groups in compartment {compartment_id}")
            return groups
            
        except Exception as e:
            logger.exception(f"Error listing groups: {e}")
            raise
  • Import statement registering the list_groups helper function for use in the MCP server.
    from mcp_server_oci.tools.identity import (
        list_users,
        get_user,
        list_groups,
        get_group,
        list_policies,
        get_policy,
        list_dynamic_groups,
        get_dynamic_group,
    )
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it's a list operation, implying read-only behavior, but doesn't disclose any behavioral traits such as pagination, rate limits, authentication requirements, or error conditions. This leaves significant gaps for an agent to understand how to invoke it correctly.

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

Conciseness4/5

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

The description is appropriately sized and front-loaded with the core purpose in the first sentence, followed by structured sections for args and returns. There's minimal waste, though the formatting with quotes and line breaks could be slightly cleaner.

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 (1 parameter, no output schema, no annotations), the description is somewhat complete but has gaps. It covers the purpose and parameter semantics adequately, but lacks behavioral transparency and usage guidelines, making it insufficient for full agent understanding without additional context.

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 context for the single parameter 'compartment_id' by explaining it's the 'OCID of the compartment to list groups from', which clarifies its role beyond the schema's basic title. With 0% schema description coverage, this compensates well, though it doesn't cover all potential parameter nuances like format or validation.

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 ('List') and resource ('all IAM groups in a compartment'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_users' or 'list_dynamic_groups', which list other IAM resources, so it doesn't reach the highest score.

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 'get_group' (which retrieves a single group) or other list tools, nor does it specify any prerequisites or exclusions for usage.

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