Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_update_user_role

Modify an existing user role by changing its alias or permission settings.

Instructions

✏️ Update user role - Modify an existing user role's alias or permissions

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": {
      "role_id": "<role_id>"
    },
    "name": "vibemk_update_user_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasNoNew display name/alias for the role
role_idYesID of the role to update
permissionsNoPermission dictionary (permission_id: boolean)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only states that the role's alias or permissions can be modified, but does not mention side effects, partial update semantics, idempotency, or auth requirements.

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 concise sentence with no redundant information or fluff. The emoji does not detract from clarity.

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

Completeness3/5

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

The description provides enough to understand the basic operation, but it does not mention what the tool returns, whether it is idempotent, or how partial updates to alias/permissions behave. Given the absence of an output schema, some additional context could be helpful.

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 schema already describes all three parameters with 100% coverage. The description adds minimal extra meaning beyond 'existing' and 'modify', but the schema covers parameter purpose adequately.

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 updates an existing user role's alias or permissions. It uses a specific verb ('Update') and resource ('user role'), and the distinction from create/delete/show role tools is clear.

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 indicates the tool is for modifying an existing role, but it does not explicitly explain when to prefer this over related tools or mention prerequisites such as the role needing to exist. Usage guidance is implied rather than explicit.

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