Skip to main content
Glama
DynamicEndpoints

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

configure_admin_consent

Configure admin consent workflow for Microsoft 365 applications to manage access permissions and ensure compliance with security policies.

Instructions

Configure admin consent workflow for applications (MS.AAD.5.3v1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'configure_admin_consent' tool. It configures the admin consent workflow by patching the Microsoft Graph API endpoint '/policies/adminConsentRequestPolicy' to enable notifications, reminders, and set a request duration.
    private async configureAdminConsent() {
      try {
        // Configure admin consent workflow using Microsoft Graph API
        await this.graphClient
          .api('/policies/adminConsentRequestPolicy')
          .patch({
            isEnabled: true,
            notifyReviewers: true,
            remindersEnabled: true,
            requestDurationInDays: 7,
          });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Admin consent workflow configured successfully',
            },
          ],
        };
      } catch (error: unknown) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to configure admin consent: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Tool registration in the listTools response, including name, description, and empty input schema.
      name: 'configure_admin_consent',
      description: 'Configure admin consent workflow for applications (MS.AAD.5.3v1)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Dispatch case in the CallToolRequest handler that routes to the configureAdminConsent method.
    case 'configure_admin_consent':
      return await this.configureAdminConsent();
  • Input schema definition for the tool, which expects an empty object.
    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 full burden. 'Configure' implies a write/mutation operation, but the description doesn't disclose behavioral traits like required permissions, whether changes are reversible, or what specific aspects of the workflow are configurable. The MS.AAD.5.3v1 reference is opaque and adds no practical context.

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

Conciseness3/5

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

The description is brief (one sentence) but includes the cryptic 'MS.AAD.5.3v1' reference that doesn't add clear value. While front-loaded with the core purpose, the reference feels like wasted space rather than earned content.

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?

For a configuration/mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'configure' entails operationally, what gets changed, or what success/failure looks like. The MS.AAD reference doesn't compensate for these gaps in behavioral 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 tool has zero parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a high baseline score since it doesn't need to compensate for any schema gaps.

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 resource ('admin consent workflow for applications'), making the purpose specific and understandable. However, it doesn't distinguish this tool from similar-sounding siblings like 'configure_global_admin_approval' or 'restrict_app_consent', which prevents a perfect 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. With multiple configuration-related siblings (configure_admin_alerts, configure_global_admin_approval, restrict_app_consent, etc.), the lack of differentiation leaves the agent without context for tool selection.

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