Skip to main content
Glama

get-role-definitions

List available Azure role definitions to manage access control and permissions for resources within your subscription or specified scope.

Instructions

List available role definitions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoScope for role definitions. Leave empty for subscription level.

Implementation Reference

  • Switch case in handleCallTool that registers and routes the 'get-role-definitions' tool call to its handler function.
    case "get-role-definitions":
      result = await this.handleGetRoleDefinitions(args);
      break;
  • Tool schema definition returned by listTools, specifying the name, description, and input schema (optional scope parameter).
    {
      name: "get-role-definitions",
      description: "List available role definitions",
      inputSchema: {
        type: "object",
        properties: {
          scope: {
            type: "string",
            description:
              "Scope for role definitions. Leave empty for subscription level.",
          },
        },
        required: [],
      },
    },
  • Primary handler implementation that parses input arguments, lists role definitions using Azure AuthorizationManagementClient.roleDefinitions.list(), formats the results, and handles errors.
    private async handleGetRoleDefinitions(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 roleDefinitions = [];
        const definitionScope =
          scope || `/subscriptions/${this.context.selectedSubscription}`;
    
        for await (const definition of this.context.authorizationClient.roleDefinitions.list(
          definitionScope
        )) {
          roleDefinitions.push({
            id: definition.id,
            name: definition.name,
            roleName: definition.roleName,
            description: definition.description,
            type: definition.type,
            permissions: definition.permissions?.map((p) => ({
              actions: p.actions,
              notActions: p.notActions,
              dataActions: p.dataActions,
              notDataActions: p.notDataActions,
            })),
          });
        }
    
        return { roleDefinitions, total: roleDefinitions.length };
      } catch (error) {
        this.logWithContext("error", `Error getting role definitions: ${error}`, {
          error,
        });
        throw new AzureResourceError(`Failed to get role definitions: ${error}`);
      }
    }
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 it's a list operation, implying it's read-only, but doesn't specify if it requires authentication, rate limits, pagination behavior, or what the output format looks like. This leaves significant gaps for a tool that interacts with role definitions.

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 that directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple list operation, making it easy to parse quickly.

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 the lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like authentication needs, error handling, or output structure, which are crucial for a tool that lists role definitions in a system like Azure. The simplicity of the tool (one optional parameter) doesn't excuse these omissions.

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?

The input schema has 100% description coverage, with the 'scope' parameter documented as 'Scope for role definitions. Leave empty for subscription level.' The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without compensating value.

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 ('available role definitions'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'list-role-assignments' or 'get-user-permissions', but the focus on definitions rather than assignments or user-specific permissions is implied through the wording.

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 like 'list-role-assignments' or 'get-user-permissions'. It lacks context about prerequisites, such as needing authentication or specific permissions, and doesn't mention any exclusions or scenarios where other tools might be more appropriate.

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