Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

get_website

Read-only

Retrieve detailed monitoring configuration for a website by its ID, including URL, checkpoints, thresholds, and SSL settings. Use to troubleshoot failed checks or audit monitoring.

Instructions

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

Returns: Complete website monitor details: name, type (webcheck/pingcheck), domain/URL, monitoring configuration, checkpoint locations, response time thresholds, SSL settings, authentication, custom headers, alert status.

When to use:

  • Review monitoring configuration

  • Check checkpoint locations

  • Verify URL and settings

  • Troubleshoot failed checks

  • Audit SSL certificate monitoring

Configuration details returned:

  • steps: Multi-step transaction monitoring (for complex workflows)

  • checkpoints: Which global locations perform checks (e.g., US-East, EU-West, Asia-Pacific)

  • schema: HTTP vs HTTPS

  • testLocation: Internal (from collector) vs External (from cloud)

  • responseTimeThreshold: Alert if slower than X ms

  • sslCertExpirationDays: Alert X days before cert expires

Use cases:

  • Verify website is monitored from correct geographic locations

  • Check if SSL certificate expiration monitoring is enabled

  • Review response time thresholds (too strict? too lenient?)

  • Troubleshoot why website checks are failing

  • Document what endpoints are monitored

Workflow: Use "list_websites" to find websiteId, then use this tool for complete monitoring configuration.

Related tools: "list_websites" (find website), "update_website" (modify), "generate_website_link" (get URL), "list_website_checkpoints" (available locations).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
websiteIdYesThe ID of the website 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.
Behavior5/5

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

Description reinforces the readOnlyHint from annotations by stating it returns data. It details what configuration is returned (steps, checkpoints, thresholds, SSL) and includes use cases for troubleshooting, adding significant context 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 sections and bullet points, but slightly verbose with multiple use case lists. The core purpose is front-loaded, and each section adds value, though some redundancy exists.

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?

Thoroughly explains return values (name, type, checkpoints, thresholds, SSL, etc.) and no output schema is present. The description covers all important aspects for a read tool, including related tools and a workflow.

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 baseline is 3. The description does not add significant new parameter-level detail beyond what the schema already provides for 'websiteId' and 'fields'.

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 verb ('Get'), resource ('website monitor'), and scope ('by its ID in LogicMonitor'). It distinguishes from sibling tools like 'list_websites' and 'update_website' by specifying unique functionality.

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 description includes explicit 'When to use' and 'Workflow' sections, listing specific scenarios (e.g., review config, troubleshoot) and suggesting using 'list_websites' first. It also lists related tools with descriptions, providing clear guidance on 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