Skip to main content
Glama
kapilduraphe

Okta MCP Server

suspend_user

Suspend a user in Okta by providing their unique user ID. This tool integrates with the Okta MCP Server to manage user access effectively.

Instructions

Suspend a user in Okta

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesThe unique identifier of the Okta user

Implementation Reference

  • The main handler function for the 'suspend_user' tool. It validates the input using Zod schema, retrieves the Okta client, calls the Okta API to suspend the user by ID, and returns a success or error message.
    suspend_user: async (request: { parameters: unknown }) => {
      const { userId } = userSchemas.suspendUser.parse(request.parameters);
    
      try {
        const oktaClient = getOktaClient();
    
        await oktaClient.userApi.suspendUser({
          userId,
        });
    
        return {
          content: [
            {
              type: "text",
              text: `User with ID ${userId} has been suspended.`,
            },
          ],
        };
      } catch (error) {
        console.error("Error suspending user:", error);
        return {
          content: [
            {
              type: "text",
              text: `Failed to suspend user: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    },
  • The tool registration object in the userTools array, defining the name, description, and input schema for the 'suspend_user' tool.
    {
      name: "suspend_user",
      description: "Suspend a user in Okta",
      inputSchema: {
        type: "object",
        properties: {
          userId: {
            type: "string",
            description: "The unique identifier of the Okta user",
          },
        },
        required: ["userId"],
      },
    },
  • Zod schema definition for 'suspendUser' input validation, used within the handler to parse and validate the request parameters.
    suspendUser: z.object({
      userId: z.string().min(1, "User ID is required"),
    }),
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. 'Suspend' implies a write operation that modifies user state, but the description doesn't specify whether this requires admin permissions, is reversible, affects user access immediately, or has side effects. This is inadequate for a mutation tool with zero annotation coverage.

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 wasted words. It's front-loaded with the core action and resource, making it immediately scannable and appropriately sized for its purpose.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what suspension entails, what the response looks like, or how it differs from similar operations. Given the complexity of user management and sibling tools, more context is needed for safe and effective use.

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 single parameter 'userId' clearly documented in the schema. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 where the schema does the heavy lifting.

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 action ('suspend') and target resource ('a user in Okta'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'deactivate_user' or 'unsuspend_user', which would require more specificity about what suspension means in this context versus deactivation.

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 'deactivate_user' or 'unsuspend_user'. It lacks context about prerequisites, consequences, or typical use cases, leaving the agent to infer usage from tool names alone.

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

Related 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/kapilduraphe/okta-mcp-server'

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