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

io.github.ryanmat/logicmonitor

by ryanmat

get_log_partitions

Read-onlyIdempotent

List LM Logs partitions with active or paused status, criteria, and contract details—state, SKU, retention, usage limit, period—to check partition state and contract limits.

Instructions

List the LM Logs partitions with whether each is active or paused, its criteria, and its active contract (state, SKU, retention, usage limit, period). Use it to check partition state and contract limits.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds value beyond them by spelling out the shape of each returned partition (state, criteria, contract fields), which is important because no output schema exists. It does not mention pagination behavior or volume, keeping it short of a 5.

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 and its returned fields before the usage note. The parenthetical enumerations are dense but each item earns its place by describing return content; no filler or repetition.

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 two-parameter read-only list tool with no output schema, the description covers what the tool returns and what it is for. The only gap is the absence of any routing hint toward the other log-related tools, which keeps it from a 5.

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% with two optional parameters (limit, offset) already documented in the schema, so baseline 3 applies. The description adds no syntax, default, or pagination semantics beyond what the schema provides.

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?

States a specific verb (List) and resource (LM Logs partitions) and enumerates the fields returned: active/paused state, criteria, and the active contract with state, SKU, retention, usage limit, and period. An agent can tell what this returns, though the description never contrasts it with log-related siblings such as get_log_pipelines or get_log_usage.

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?

The second sentence ('Use it to check partition state and contract limits') gives an implied usage context but no explicit when-not condition and no named alternative. Guidance is adequate but leaves the agent to infer that other log tools cover different resources.

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