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

io.github.ryanmat/logicmonitor

by ryanmat

get_ops_note

Read-onlyIdempotent

Retrieve details for a specific LogicMonitor ops note by note ID to review operational context, annotations, and troubleshooting information.

Instructions

Get details about a specific ops note

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": {
      "note_id": "<note_id>"
    },
    "name": "get_ops_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYesOps note ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.0.1
    • addedInput schema / properties / note_id / pattern
      Added value: +"^[A-Za-z0-9_-]+$"
    • changedInput schema / properties / note_id / type
      Previous value: -"integer"New value: +"string"
  2. First observedv4.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is covered. The description adds nothing beyond that: it does not say what happens when note_id does not exist, whether the ID comes from a lookup call, or what kind of detail is returned. With no output schema, that silence leaves the return content entirely opaque.

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?

One short sentence, front-loaded and free of filler or redundancy. It is efficient, though efficiency here reflects how little is said rather than disciplined editing of substantive content.

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?

This is a simple one-parameter read tool whose annotations fully cover the safety profile, so the bar is low. Still, as a 'get details' tool with no output schema, the description should at least sketch what details are returned or the not-found behavior; it does neither.

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 the single note_id parameter is documented with its pattern in the schema, so the baseline of 3 applies. The description contributes no additional semantics such as where note IDs originate or how they are formatted.

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

Purpose4/5

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

The description states a specific verb ('Get') and resource ('ops note') and scopes it to a single note ('a specific ops note'), which implicitly separates it from the list-style get_ops_notes. It stops short of explicitly naming or contrasting that sibling, so differentiation is implied rather than stated.

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 when-to-use guidance: nothing says to call this when you have a known note_id versus browsing with get_ops_notes, and no exclusions or prerequisites are given. A single schema parameter makes the intent guessable, which is the only thing carrying usage here.

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