Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

by monitoringartist
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

get_dashboard

Read-only

Retrieve detailed configuration of a LogicMonitor dashboard, including widgets, owner, group, and template variables, for review or cloning.

Instructions

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

Returns: Complete dashboard details: name, description, groupId, owner, widgets configuration, widget count, sharing settings, template variables, last modified.

When to use:

  • Review dashboard configuration

  • See widget definitions before cloning

  • Check dashboard owner

  • Verify template variables

  • Get dashboard metadata

What you get:

  • widgetsConfig: JSON configuration of all widgets (chart types, metrics, thresholds)

  • widgetTokens: Template variables (e.g., defaultDeviceGroup for dynamic filtering)

  • groupId/groupName: Which folder dashboard is in

  • sharable: Whether dashboard is public/private

Use cases:

  • Clone dashboard to create similar one

  • Export dashboard configuration for backup

  • Audit which resources/devices/metrics are being visualized

  • Document dashboard purpose and widgets

Workflow: Use "list_dashboards" to find dashboardId, then get details, then "generate_dashboard_link" to get shareable URL.

Related tools: "list_dashboards" (find dashboard), "generate_dashboard_link" (get URL), "update_dashboard" (modify), "list_dashboard_groups" (browse folders).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dashboardIdYesThe ID of the dashboard 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.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true. Description adds detailed behavioral context: lists returned fields (widgetsConfig, widgetTokens, groupId, sharable) and use cases, confirming no side effects.

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 sections and bullet points. Slightly long but each section adds value. Could be more concise but remains clear and front-loaded.

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, description fully explains return content, use cases, and workflow. No gaps for an agent to understand and invoke this tool correctly.

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 covers 100% of parameters. Description adds value by explaining how to find dashboardId via list_dashboards and that fields parameter can limit response, but does not elaborate 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?

Clearly states verb 'Get', resource 'dashboard details', and domain 'LogicMonitor monitoring'. Distinguishes from siblings by specifying it's for dashboard retrieval and referencing related tools like list_dashboards.

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?

Provides explicit 'When to use' bullet points and a workflow (list_dashboards -> get_dashboard -> generate_dashboard_link). Also lists related tools for alternative actions.

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