Skip to main content
Glama
io.github.ryanmat/logicmonitor

io.github.ryanmat/logicmonitor

by ryanmat

get_dashboard

Read-onlyIdempotent

Retrieve detailed information for a specific LogicMonitor dashboard, including its portal link or full widget configuration, by providing the dashboard ID.

Instructions

Get detailed information about a specific dashboard

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dashboard_id": "<dashboard_id>"
    },
    "name": "get_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the REST object with its widgets under widgets_full, the template create_dashboard clones, instead of the object with its portal link
dashboard_idYesDashboard ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / raw
      Added value: +{
      +  "default": false,
      +  "description": "Return the REST object with its widgets under widgets_full, the template create_dashboard clones, instead of the object with its portal link",
      +  "type": "boolean"
      +}
  2. First observedv4.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — it does not explain the two distinct output shapes implied by the raw flag or what "detailed" encompasses, so the description contributes no behavioral context of its own.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity edges toward under-specification rather than ideal conciseness.

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

Completeness3/5

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

With no output schema, the description ideally should indicate what "detailed information" includes, especially since the raw flag switches between two return shapes. The schema covers parameters well and annotations cover safety, so the definition is usable, but the return-content gap leaves it only minimally complete.

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 description coverage is 100%, so both dashboard_id and the raw flag are fully documented in the schema, including the widgets_full versus portal-link distinction. The description mentions neither parameter, so it adds no meaning beyond structured data; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get ... a specific dashboard"), which is better than a bare tautology, but "detailed information" is vague about what is actually returned. It offers no differentiation from siblings like get_dashboard_widgets or get_dashboard_group, which an agent could easily confuse with this tool.

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?

There is no guidance on when to use this tool versus the widget-specific or group-level siblings, and no prerequisites or exclusions are stated. The agent must infer usage purely from the name.

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