Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_list_user_roles

List all user roles (built-in and custom) to review access permissions and manage user capabilities in your monitoring setup.

Instructions

👥 List user roles - Show all available user roles (built-in and custom)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vibemk_list_user_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
show_builtinNoInclude built-in roles (admin, user, guest) in the list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. The verb 'List' implies a read-only operation, but the description does not explicitly state that it has no side effects, nor does it mention any permissions, rate limits, or potential errors. It is clear enough for a basic list operation but lacks explicit safety guarantees.

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 concise and to the point, using one line to convey the action and scope. The emoji adds visual cue without redundancy, and there is no unnecessary filler.

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

Completeness5/5

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

For a simple list operation with no output schema, the description is complete. It tells the agent exactly what the tool returns (a list of user roles) and the optional parameter is fully described in the schema. No additional context is needed.

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 provides a description for the single parameter `show_builtin` ('Include built-in roles (admin, user, guest) in the list'), giving 100% coverage. The tool description does not add extra meaning, but the schema description is sufficient, warranting the baseline score of 3.

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 action ('List') and the resource ('user roles'), and specifies the scope ('all available' and 'built-in and custom'). This distinguishes it from sibling tools like `vibemk_show_user_role` which likely targets a single role.

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?

The description does not provide any guidance on when to use this tool versus alternatives such as `vibemk_show_user_role` or `vibemk_get_users`. There is no mention of conditions, prerequisites, or scenarios where this listing is preferred.

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