Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

get_role

Read-only

Get detailed permissions for a role by its ID to audit security, compare roles, or enforce least privilege.

Instructions

Get detailed information about a specific role by its ID in LogicMonitor (LM) monitoring.

Returns: Complete role details: name, description, custom flag, detailed permission matrix (view/manage/delete/acknowledge for each area: resources/devices, alerts, dashboards, reports, settings, users).

When to use:

  • Review exact permissions before assigning role

  • Compare roles to choose correct one

  • Document security policies

  • Audit what a role can/cannot do

  • Before creating custom role (use as template)

Permission granularity returned:

  • Resources: Can view/add/modify/delete resource/device

  • Alerts: Can view/acknowledge/manage alert rules

  • Dashboards: Can view/create/edit/delete dashboards

  • Reports: Can view/create/schedule reports

  • Settings: Can modify datasources/collectors/integrations

  • Users: Can manage other users/roles

Use cases:

  • Security audit: "Can this role delete production resources/devices?"

  • Least privilege: Choose role with minimal required permissions

  • Documentation: Export role permissions for compliance

  • Role comparison: Compare multiple roles to find right fit

Workflow: Use "list_roles" to find roleId, then use this tool to review detailed permissions before assigning to users.

Related tools: "list_roles" (find roles), "list_users" (see who has this role), "create_role" (create custom role).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleIdYesThe ID of the role to retrieve
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. The description adds detail on the permission matrix returned, but no behavioral surprises. Some extra context on return format adds value beyond annotations.

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?

Well-structured with headings and bullet points, front-loading the main purpose. Slightly lengthy but each section earns its place with examples and use cases.

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?

Despite no output schema, the description thoroughly explains the return format (permission matrix), covers workflow, and lists use cases. Comprehensive for the tool's complexity.

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 100%, so parameters are fully described in schema. The description does not add new information about parameters beyond what the schema provides, meeting the baseline.

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 retrieves role details by ID. It uses specific verb 'Get' and resource 'role', and distinguishes from siblings by mentioning related tools like list_roles and create_role.

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 (review permissions, audit, compare) and provides workflow: use list_roles to find roleId first. Also names related tools (list_roles, list_users, create_role) for context.

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