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

io.github.ryanmat/logicmonitor

by ryanmat

get_usage_metrics

Read-onlyIdempotent

Reads current counts of devices, Kubernetes, AWS, Azure, and GCP resources, websites, and services in the LogicMonitor portal, noting these point-in-time figures are not billed amounts.

Instructions

Read how many devices, Kubernetes, AWS, Azure and GCP resources, websites and services the portal holds now, as point-in-time counts. The portal is billed on each feature's roll-up basis in the contract, so these are not billed figures.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond them: the values are a snapshot of 'now' and are explicitly not the contractual roll-up figures used for billing, which prevents misreading the numbers. Return shape and enumeration granularity are still unexplained.

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?

Two sentences, front-loaded with the resource enumeration and ending with the crucial billing caveat. The second sentence is slightly dense ('billed on each feature's roll-up basis in the contract') but every clause carries a distinct fact. 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 zero-parameter, read-only counter tool with rich annotations and no output schema, the description covers what is counted and what the numbers mean, which is the main risk of misinterpretation. Only the response shape (unit of count, per-feature breakdown) is left unspecified, a minor gap given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a single unfiltered call across all resource categories rather than a scoped query.

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 ('Read how many...') and enumerates exactly what is counted: devices, Kubernetes/AWS/Azure/GCP resources, websites and services. It also pins the semantics as 'point-in-time counts' and explicitly separates them from billed figures, which distinguishes it from billing-oriented siblings such as get_usage_contract. It stops short of naming a sibling to use instead, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this is the tool for a current inventory snapshot, and the closing clause signals it is not the tool for billing numbers. There is no explicit 'use this when X, use get_usage_contract when Y' routing, and no prerequisites are mentioned. Adequate but leaves the alternative selection to inference.

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