VibeAdmin

Change a user's role

change_user_role

Destructive

Change a user's role in the customer's app (e.g. user, admin).

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_id": "<user_id>",
      "role": "<role>"
    },
    "name": "change_user_role"
  }
}

Input Schema

Name	Required	Description	Default
`role`	Yes
`user_id`	Yes	The user's id in your app (preferred) or the VibeAdmin id from list_users.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's silence on irreversibility, permission requirements, or what happens to a user's existing access is a real gap. The only added behavioral detail is the app-scoping phrase; nothing warns the agent that this replaces a user's current role.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with no filler, front-loading the action. It is efficient but so short that it omits information an agent would need.

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?

With no output schema and a destructive mutation annotation, the description should carry more weight about effects and constraints. As written, an agent knows only the verb, target scope, and two sample role values.

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 50%: user_id is documented, but role has only a maxLength and no enum. The description partially compensates with example values ('user, admin'), though it does not indicate whether roles are free-form or constrained to a configured set.

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 ('Change a user's role') and scopes it to 'the customer's app', which separates it from account-level siblings like set_config or add_credits. It stops short of differentiating from adjacent user-mutating tools such as suspend_user or update_user_metadata.

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?

There is no guidance on when to use this instead of alternatives like suspend_user, restore_user, or update_user_metadata, and no prerequisites (e.g. that the user must exist or that the role must be pre-defined) are mentioned.

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

All VibeAdmin tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.