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

io.github.ryanmat/logicmonitor

by ryanmat

get_ops_notes

Read-onlyIdempotent

Lists operations notes with pagination and optional tag filtering so you can review operational context and history.

Instructions

List ops notes

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_ops_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
tag_filterNoFilter by tag (substring match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.0.1
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Pagination offset",
      +  "type": "integer"
      +}
    • addedInput schema / properties / tag_filter
      Added value: +{
      +  "description": "Filter by tag (substring match)",
      +  "type": "string"
      +}
  2. First observedv4.2.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no note about ordering, pagination behavior, or what an open-world listing entails.

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

Conciseness3/5

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

Three words with zero padding, so there is nothing to trim, but the brevity is under-specification rather than discipline. Nothing is front-loaded because nothing beyond the resource name is stated.

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

Completeness2/5

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

For a paginated, tag-filterable listing tool with three parameters and no output schema, the definition says nothing about what a note contains, how results are ordered, or how pagination terminates. The annotations cover safety but not the usage surface an agent needs.

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 limit, offset and tag_filter are documented in the schema itself, which sets the baseline at 3. The description contributes no additional meaning about filtering semantics, but it is not penalized for deferring to a complete schema.

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

Purpose2/5

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

"List ops notes" is essentially the tool name restated as a verb phrase; it names no scope, no content type, and does not distinguish this list operation from the singular sibling get_ops_note. An agent learns only that it returns a collection, which the plural name already implies.

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, no mention of when to prefer get_ops_note versus this listing tool, and no prerequisites or exclusions. The presence of a singular sibling makes the missing routing guidance a real gap.

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