Skip to main content
Glama

list-role-assignments

View Azure role assignments at subscription, resource group, or resource level to manage access control and permissions.

Instructions

List role assignments for the subscription or resource group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoScope for role assignments (subscription, resource group, or resource ID). Leave empty for subscription level.

Implementation Reference

  • Tool registration including name, description, and input schema definition in handleListTools() method.
    {
      name: "list-role-assignments",
      description:
        "List role assignments for the subscription or resource group",
      inputSchema: {
        type: "object",
        properties: {
          scope: {
            type: "string",
            description:
              "Scope for role assignments (subscription, resource group, or resource ID). Leave empty for subscription level.",
          },
        },
        required: [],
      },
    },
  • Main handler function that parses input, lists role assignments using Azure AuthorizationManagementClient.roleAssignments.listForScope, and returns formatted results.
    private async handleListRoleAssignments(args: any) {
      const { scope } = z
        .object({
          scope: z.string().optional(),
        })
        .parse(args);
    
      if (!this.context.authorizationClient) {
        throw new AzureMCPError(
          "Authorization client not initialized",
          "NO_CLIENT"
        );
      }
    
      try {
        const roleAssignments = [];
        const assignmentScope =
          scope || `/subscriptions/${this.context.selectedSubscription}`;
    
        for await (const assignment of this.context.authorizationClient.roleAssignments.listForScope(
          assignmentScope
        )) {
          roleAssignments.push({
            id: assignment.id,
            principalId: assignment.principalId,
            principalType: assignment.principalType,
            roleDefinitionId: assignment.roleDefinitionId,
            scope: assignment.scope,
            createdOn: assignment.createdOn,
            createdBy: assignment.createdBy,
          });
        }
    
        return { roleAssignments, total: roleAssignments.length };
      } catch (error) {
        this.logWithContext("error", `Error listing role assignments: ${error}`, {
          error,
        });
        throw new AzureResourceError(`Failed to list role assignments: ${error}`);
      }
    }
  • Dispatch case in handleCallTool switch statement that routes to the handler.
    case "list-role-assignments":
      result = await this.handleListRoleAssignments(args);
      break;
  • Input schema validation using Zod in the handler function.
    const { scope } = z
      .object({
        scope: z.string().optional(),
      })
      .parse(args);
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 it's a list operation, implying read-only behavior, but doesn't disclose critical traits like authentication requirements, rate limits, pagination, or what happens if scope is invalid. For a tool with no annotations, this leaves significant behavioral gaps.

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 a single, efficient sentence with zero waste. It's front-loaded with the core purpose and appropriately sized for a simple list tool. Every word earns its place, making it highly concise and well-structured.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances. For a tool that likely returns a list of assignments with potential complexity, more context is needed to be fully helpful to an AI agent.

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 description coverage is 100%, with the parameter 'scope' fully documented in the schema. The description adds minimal value beyond the schema by mentioning 'subscription or resource group' context, but doesn't provide additional semantics like examples or edge cases. Baseline 3 is appropriate given high schema coverage.

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 ('role assignments') with scope context ('for the subscription or resource group'). It distinguishes from siblings like 'get-role-definitions' (definitions vs assignments) and 'get-user-permissions' (permissions vs assignments). However, it doesn't explicitly differentiate from all siblings, keeping it at 4 rather than 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 mentions scope but doesn't specify when to use 'list-role-assignments' over 'get-user-permissions' or other sibling tools. There are no explicit when/when-not instructions or named alternatives, resulting in minimal guidance.

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/kalivaraprasad-gonapa/azure-mcp'

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