Skip to main content
Glama

revoke_role

Destructive

Revoke a directly granted role from a ServiceNow user by specifying the user and role; requires WRITE_ENABLED=true.

Instructions

Revoke a directly-granted role from a user. Requires WRITE_ENABLED=true

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": {
      "user": "<user>",
      "role": "<role>"
    },
    "name": "revoke_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesRole sys_id or name
userYesUser sys_id, user_name, or email

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.15.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the risk profile is covered. The description adds genuinely new context the annotations cannot express: the tool requires WRITE_ENABLED=true to function. It could go further on non-idempotency and failure behavior, but the environment precondition is real added value.

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 short sentences, the action first and the operational prerequisite second. No filler, no repetition of the name or the schema.

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?

For a two-parameter destructive mutation with full annotation coverage and no output schema, the description covers the action and the environment gate. Only non-idempotency consequences and error semantics are unaddressed, which are minor given the annotation set.

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 both 'role' and 'user' documented including accepted identifier formats. The description adds no format or constraint detail beyond what the schema already provides, so the baseline 3 applies.

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 states a specific verb and resource ('Revoke a directly-granted role from a user'), and the qualifier 'directly-granted' distinguishes this from granting or role creation without naming a sibling. It is clear what the tool does, though it stops short of explicitly contrasting with grant_role.

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 phrase 'directly-granted' implies this tool should not be used for inherited/indirect role assignments, which is useful implicit scoping. However, there is no explicit when-to-use or when-not guidance and no named alternative for the inverse operation.

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

Deploy Server

Other Tools