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

io.github.ryanmat/logicmonitor

by ryanmat

get_usage_contract

Read-onlyIdempotent

Read a LogicMonitor portal's contracted entitlements to answer license and contract questions: every named feature, its role, entitled quantity, unit, roll-up basis, and detected billing mode.

Instructions

Read the portal's contracted entitlements, for license and contract questions: every feature the contract names, entitled or not, each with its role (billable_line, metered_no_entitlement, metered_unpaid, repeats_parent, rollup_or_carveout), entitled quantity, unit and roll-up basis, plus the detected billing_mode. It does not count the portal's current resources.

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

Input Schema

NameRequiredDescriptionDefault
billable_onlyNoReturn only the billable_line features

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.2/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 the description adds real substance beyond them: the enumerated role taxonomy (billable_line, metered_no_entitlement, metered_unpaid, repeats_parent, rollup_or_carveout) and detection of billing_mode. It does not discuss pagination or the output's shape, so not 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.

Conciseness5/5

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

One front-loaded sentence with the purpose first, the scope exclusion last, and the role enumeration earning its length by telling the agent exactly what categories to expect. 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 one-optional-param read tool with no output schema, the description effectively narrates the returned fields (roles, entitled quantity, unit, roll-up basis, billing_mode). Only pagination/response-volume behavior is unaddressed, a minor gap.

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?

The single parameter is fully documented in the schema (100% coverage), so the schema carries the meaning. The description never mentions the billable_only filter, adding nothing beyond the structured field, which is the baseline-3 case.

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 ('Read') and a precise resource ('the portal's contracted entitlements'), and scopes it to license/contract questions. The closing clause 'It does not count the portal's current resources' explicitly separates it from usage/metric siblings, so an agent can select it without opening any schema.

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 a clear when-to-use condition ('for license and contract questions') and a when-not signal by disclaiming current-resource counting. It stops short of naming a concrete alternative tool to use for counting resources, so it is clear but not fully routing.

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