Skip to main content
Glama
DynamicEndpoints

BOD-25-01-CSA-Microsoft-Policy-MCP

configure_global_admin_approval

Configure approval requirements for Global Administrator activation to enforce security controls and meet compliance standards.

Instructions

Configure approval requirement for Global Administrator activation (MS.AAD.7.6v1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that executes the tool logic: patches the role management policy via Microsoft Graph API to require approval for Global Administrator activation.
    private async configureGlobalAdminApproval() {
      try {
        // Configure approval settings using Microsoft Graph API
        await this.graphClient
          .api('/policies/roleManagementPolicies')
          .patch({
            requireApprovalForGlobalAdmin: true,
            approvalWorkflowEnabled: true,
          });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Global Administrator approval requirement configured successfully',
            },
          ],
        };
      } catch (error: unknown) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to configure Global Admin approval: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Tool registration in the ListTools response, defining the tool name, description, and input schema.
    {
      name: 'configure_global_admin_approval',
      description: 'Configure approval requirement for Global Administrator activation (MS.AAD.7.6v1)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Dispatch case in the CallToolRequest handler that routes to the tool's handler method.
    case 'configure_global_admin_approval':
      return await this.configureGlobalAdminApproval();
  • Input schema definition for the tool (empty object, no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
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 of behavioral disclosure. While 'configure' implies a write/mutation operation, the description does not specify whether this requires elevated permissions, if changes are reversible, what the default state is, or any side effects. The policy reference hints at compliance but lacks operational details needed for safe invocation.

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 fluff or redundant information. It is appropriately sized for a no-parameter tool and front-loads the essential action ('configure').

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 complexity of an administrative configuration tool with no annotations and no output schema, the description is insufficient. It lacks critical information such as required permissions, system impact, success/failure indicators, or how to verify the configuration. The policy reference adds some context but does not compensate for these gaps in operational guidance.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose. A baseline score of 4 is applied since the schema fully covers the absence of parameters, and the description does not add unnecessary details.

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 'configure' and the resource 'approval requirement for Global Administrator activation', providing a specific purpose. However, it does not distinguish this tool from its many sibling configuration tools (e.g., configure_admin_consent, configure_role_alerts), which all share similar naming patterns and administrative functions.

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 a specific policy reference ('MS.AAD.7.6v1'), which might imply a regulatory or compliance context, but does not explicitly state when this configuration is needed, what prerequisites exist, or how it differs from other sibling tools like configure_admin_consent or configure_global_admins.

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/DynamicEndpoints/Automated-BOD-25-01-CISA-Microsoft-Policies-MCP'

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