Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_roles

Read-only

Retrieve all roles and their permissions to manage user assignment and audit access control in LogicMonitor.

Instructions

List all roles (permission sets) in LogicMonitor (LM) monitoring.

Returns: Array of roles with: id, name, description, custom flag, associated users count, permissions (view/manage/delete for resources/alerts/reports/settings).

What are roles: Permission templates assigned to users. Control who can view/modify/delete resources, alerts, dashboards, settings. Essential for RBAC (role-based access control).

When to use:

  • Discover available roles before creating users

  • Audit permission structure

  • Find role IDs for user assignment

  • Compare custom vs built-in roles

  • Compliance documentation

Built-in roles (examples):

  • administrator: Full access to everything

  • readonly: View-only access to monitoring data

  • manager: Manage resources/devices/alerts but not settings

Custom roles: Organizations create custom roles for specific needs (e.g., "database-team-role", "view-prod-only").

Common use cases:

  • "What roles exist?" → List all to see options

  • "Who can delete resources/devices?" → Check which roles have delete permissions

  • "Create read-only user" → Find "readonly" role ID for user creation

Workflow: Use this tool to discover roles, then "get_role" for detailed permissions, then use in "create_user" or "update_user".

Important: A negative "total" value in the response indicates incomplete results. Use pagination (size/offset parameters) or set autoPaginate: true to retrieve all items.

Related tools: "get_role" (detailed permissions), "list_users" (see user assignments), "create_user" (assign roles to new users).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoNumber of results per page (default: 50, max: 1000).
offsetNoStarting offset for pagination (default: 0). Use this to skip a specific number of results.
autoPaginateNoAutomatically fetch all pages (default: false). When true, fetches all results across multiple pages. When false, returns only the requested page. Use false for large result sets to avoid long response times.
filterNoFilter expression using LogicMonitor query syntax. Examples: name:*prod*, displayName~*server*, id>100, hostStatus:normal. Available operators: : (equals), ~ (includes), !: (not equals), !~ (not includes), >: (greater than or equals), <: (less than or equals), > (greater than), < (less than). Multiple conditions: Use comma (,) for AND, use || for OR. Do NOT use &&.
fieldsNoComma-separated list of fields to include in response. Examples: "id,displayName,hostStatus" or use "*" for all fields. Omit this parameter to receive a curated set of commonly used fields.
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds behavior beyond: notes that a negative 'total' indicates incomplete results, explains pagination and autoPaginate, and mentions result shape. This supplements the annotation with practical behavioral details.

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

Conciseness3/5

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

Well-structured with sections, but somewhat lengthy. Contains explanatory text like 'What are roles' which may be extraneous. Could be more concise without losing key 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?

With 5 parameters, no output schema, and read-only annotation, description provides sufficient context: return shape, pagination, filter syntax, common use cases, and workflow. Lacks error handling or rate limits, but overall complete for typical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good descriptions. Description adds extra meaning: explains filter syntax with examples, autoPaginate behavior, and fields parameter usage. Enhances understanding beyond schema.

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 'List all roles (permission sets) in LogicMonitor (LM) monitoring.' It specifies verb (list) and resource (roles), and differentiates from siblings by referencing related tools like get_role and create_user.

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

Usage Guidelines5/5

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

Explicitly lists when to use: discover roles before creating users, audit permissions, find role IDs, compare roles, compliance. Provides workflow: use this tool, then get_role, then create_user. Offers clear context and alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/monitoringartist/logicmonitor-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server