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

io.github.ryanmat/logicmonitor

by ryanmat

get_website_checkpoints

Read-onlyIdempotent

List a portal's website checkpoint locations to identify where website checks run from and retrieve each location's smg_id for use in get_website.

Instructions

List the portal's website checkpoint locations, the places website checks run from; each id is the smg_id a website's checkpoints carry in get_website.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_website_checkpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious semantics beyond that: that the listed ids are the same smg_id values used by get_website, which is a data-model fact annotations cannot express. It stops short of saying whether the list is portal-complete or how large it typically is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the resource named first and the clarifying definition and id-mapping appended, with no filler. Every clause carries information an agent needs.

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

Completeness4/5

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

For a simple two-optional-parameter read tool with full schema coverage, the description covers purpose, the nature of the returned items, and the key relationship to get_website. It does not describe what fields a checkpoint location carries, which matters slightly since there is no output schema.

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% and both parameters (limit, offset) already carry descriptions and defaults, so the schema does the heavy lifting. The description adds nothing about pagination behavior or recommended page sizes, leaving it at the baseline for a fully documented 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?

The description gives a specific verb ('List') and resource ('website checkpoint locations') and then defines the resource in plain terms ('the places website checks run from'). It further distinguishes itself from the sibling get_website by explaining that the returned ids are the smg_id values that get_website's checkpoints carry, so an agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The cross-reference to get_website effectively tells the agent when to reach for this tool: to resolve or interpret smg_id values encountered on a website. There is no explicit when-not or exclusion, and no mention of how this relates to other sibling listing tools, so it falls short of a full routing rule.

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