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

io.github.ryanmat/logicmonitor

by ryanmat

get_otlp_metric_names

Read-onlyIdempotent

Lists native OpenTelemetry metric names, optionally filtered by substring, to identify which OTLP metrics to query or analyze in LogicMonitor.

Instructions

List the names of metrics ingested through native OpenTelemetry (OTLP), optionally those containing a substring, to find what to query with query_otlp_metrics or analyze_metric(source="otlp"). A portal without OTLP Metrics answers with available: false

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

Input Schema

NameRequiredDescriptionDefault
endNoWindow end, unix epoch seconds
limitNoMax results
startNoWindow start, unix epoch seconds
containsNoSubstring filter on metric names (wildcards unsupported)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a portal without OTLP Metrics answers with 'available: false', which tells the agent how a non-error empty case looks. It does not describe the success payload shape, but the added edge-case disclosure is meaningful.

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 dense sentence that front-loads the verb and resource, then the discovery purpose, then the failure mode. Slightly run-on, but every clause carries information and there is no filler.

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 4-parameter, zero-required read tool with no output schema, the definition covers purpose, routing, and the empty-portal response well enough to call it correctly. Only the success return format and pagination/limit semantics are unstated, which are minor gaps.

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 coverage is 100%, so start/end/limit/contains are fully documented in the schema itself. The description only restates the optional substring filter and notes wildcards are unsupported, which the schema already says, so it adds little beyond the structured fields. Baseline 3 applies.

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?

States a specific verb and resource ('List the names of metrics ingested through native OpenTelemetry (OTLP)') and scopes it to discovery for later querying. It names the sibling tools (query_otlp_metrics, analyze_metric with source="otlp") so an agent can tell it apart from the actual query tools without opening schemas.

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?

Gives clear usage context: use this first to discover which metric names exist before calling query_otlp_metrics or analyze_metric. It does not spell out exclusions (e.g. when to prefer get_otlp_metric_labels instead), but the routing intent is explicit.

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