lab-mcp-identity-server

provision_user

Provision a new Okta user in STAGED status with required login (email) and display name, and optional justification. Audited and additive.

Instructions

Provision a new Okta user in STAGED status (Tier 2, additive, audited).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "login": "<login>",
      "displayName": "<displayName>"
    },
    "name": "provision_user"
  }
}

Input Schema

Name	Required	Description
`login`	Yes	User login (email)
`displayName`	Yes	Display name
`justification`	No	Optional justification

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions the staged status and that it is additive and audited, but it omits details like idempotency, error behavior, or permission requirements. Provides baseline but not comprehensive.

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, well-structured sentence that front-loads the action and key details. Every word adds value, and following sentences are unnecessary for this simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (3 parameters, no output schema, no nested objects), the description covers purpose, status, and operational properties. It lacks error handling or prerequisite details but is largely complete for agent invocation.

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 meaningful property descriptions. The tool description adds no additional parameter-level information beyond what the schema already provides, so it meets the baseline but does not exceed it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Provision', the resource 'new Okta user', and specifies the status 'STAGED', along with context (Tier 2, additive, audited). This distinguishes it from siblings like deactivate_user or grant_access, making the tool's purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for initial user creation but does not explicitly state when to use it versus alternatives. No exclusion or when-not-to-use guidance is provided, though sibling names help infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server