lab-mcp-identity-server

revoke_access

Request revocation of a user's group membership. Submits a pending approval that requires authorization before execution.

Instructions

Request revoke of group membership (Tier 3). Creates a pending approval; does not execute.

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": {
      "userId": "<userId>",
      "group": "<group>",
      "justification": "<justification>"
    },
    "name": "revoke_access"
  }
}

Input Schema

Name	Required	Description
`group`	Yes	Group name
`userId`	Yes	Okta user id
`justification`	Yes	Required justification

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description discloses key behavior: it is a non-executing request that requires approval. Additional details like follow-up actions or prerequisites are missing, but the core behavioral trait is clear.

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?

Two sentences efficiently convey purpose and key behavioral constraint with no redundant information.

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 low complexity (3 required params, no nested objects, no output schema), the description covers purpose and behavior adequately. It lacks mention of return values or prerequisites, but these are not critical for a simple request tool.

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 coverage is 100% with basic parameter descriptions. The tool description adds context ('group membership', 'Tier 3') but does not enhance understanding of individual parameters beyond what the schema provides.

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 tool requests revocation of group membership and contrasts with sibling tools like grant_access by specifying it creates a pending approval without immediate execution.

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

Usage Guidelines4/5

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

The description notes the tool creates a pending approval and does not execute, providing context for use in approval workflows, but does not explicitly state when not to use or list alternatives like immediate revocation methods.

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

Deploy Server