Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

by monitoringartist
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

get_access_group

Read-only

Retrieve detailed information about an access group, including its resources and assigned users, to audit access control before making changes.

Instructions

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

Returns: Complete access group details: name, description, tenant ID, list of associated resources (which resources/devices/groups are in this access group), list of users assigned to this access group.

When to use:

  • Review which resources are in this access group

  • Check which users have access to this group

  • Audit access control before modifications

  • Verify tenant isolation configuration

Key information returned:

  • Resources: Which resource/device groups and resources users in this access group can see

  • Users: Which users are assigned to this access group

  • Tenant ID: Multi-tenant identifier (MSP environments)

Impact analysis: Before modifying access group:

  • Removing resource: Users lose visibility to those resource/device

  • Removing user: User loses visibility to all resources in group

  • Deleting group: All users lose their access scope

Workflow: Use "list_access_groups" to find accessGroupId, then use this tool to review complete configuration before modifications.

Related tools: "list_access_groups" (find groups), "update_access_group" (modify), "list_users" (see user access).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accessGroupIdYesThe ID of the access group 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.

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds value by detailing the return data (resources, users, tenant ID) and providing impact analysis context. It does not contradict annotations; however, it could mention pagination or rate limits.

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?

The description is well-structured with clear sections and front-loaded purpose. While slightly verbose, every section adds value. It is efficient given the complexity.

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?

Given no output schema, the description thoroughly explains return values and provides workflow and impact context. It is complete for a read-only detail tool.

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 the schema fully describes parameters. The description provides minimal extra insight (e.g., using list_access_groups to find accessGroupId). Baseline 3 is appropriate as the schema does most of the work.

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 'Get detailed information about a specific access group... by its ID,' which is a specific verb+resource. It distinguishes itself from siblings like list_access_groups and update_access_group by explicitly mentioning them as related tools and providing usage guidance.

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?

The 'When to use' section lists specific scenarios, and the 'Workflow' section advises using list_access_groups first. It also includes 'Impact analysis' for pre-modification context, making it clear when to use this read-only tool versus 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