Skip to main content
Glama
DynamicEndpoints

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

configure_authenticator_context

Configure Microsoft Authenticator to display login context for enhanced security verification during authentication processes.

Instructions

Configure Microsoft Authenticator to show login context (MS.AAD.3.3v1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'configure_authenticator_context' tool. It patches the Microsoft Graph API's authenticationMethodsPolicy to enable the Microsoft Authenticator with context information in notifications.
    private async configureAuthenticatorContext() {
      try {
        // Configure Microsoft Authenticator settings using Microsoft Graph API
        await this.graphClient
          .api('/policies/authenticationMethodsPolicy')
          .patch({
            policies: {
              microsoftAuthenticator: {
                isEnabled: true,
                showContextInformationInNotifications: true,
              },
            },
          });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Microsoft Authenticator context information configured successfully',
            },
          ],
        };
      } catch (error: unknown) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to configure Authenticator context: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Registration of the tool in the ListToolsRequestSchema handler, specifying the name, description, and input schema (empty object, no parameters required).
    {
      name: 'configure_authenticator_context',
      description: 'Configure Microsoft Authenticator to show login context (MS.AAD.3.3v1)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema definition for the tool, which is an empty object indicating no input parameters are required.
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • Dispatcher case in the CallToolRequestSchema handler that routes the tool call to the specific handler function.
    case 'configure_authenticator_context':
      return await this.configureAuthenticatorContext();
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a configuration action but doesn't clarify whether this requires admin permissions, if it's reversible, what side effects it might have, or any rate limits. For a tool that likely modifies system settings, this is a significant gap in transparency.

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 states the purpose without any wasted words. It's appropriately sized for a zero-parameter configuration tool and gets straight to the point.

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 this is a configuration tool with no annotations and no output schema, the description should provide more context about what the tool actually does, what 'login context' means, and what the expected outcome is. The current description is too minimal for a tool that likely modifies authentication settings in a production environment.

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 the schema already fully documents the parameter situation. The description doesn't need to explain any parameters, and it appropriately doesn't attempt to do so. A baseline of 4 is appropriate for zero-parameter tools.

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 'Microsoft Authenticator' with the specific purpose 'to show login context', which is more specific than just restating the name. However, it doesn't differentiate from sibling tools like 'configure_admin_alerts' or 'configure_admin_consent' that also configure settings, leaving room for improvement.

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 prerequisites, timing considerations, or relationships to other configuration tools in the sibling list, leaving the agent with no usage context beyond the basic purpose.

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