cmms-mcp-server

list_alarms

Read-onlyIdempotent

Retrieve CMMS alarms ranked by severity and recency, with filters for severity, state, asset, and time, plus pagination for triage and monitoring.

Instructions

List alarms, most severe and most recent first.

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": "list_alarms"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size (1-100).
`since`	No	Only alarms raised at or after this ISO-8601 time (UTC if no zone).
`state`	No	'active' means nobody has acknowledged it yet.
`offset`	No	Items to skip; use next_offset from the previous page.
`asset_id`	No	Only alarms of this asset, e.g. AST-0001.
`severity`	No	Filter by severity.

Output Schema

Name	Required	Description	Default
`items`	Yes
`total`	Yes
`next_offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is fully covered without description help. The description's contribution is the default sort order and implicit paging behavior, which is useful but thin; it says nothing about what a page contains or default filter behavior (e.g., whether cleared alarms are included).

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?

A single front-loaded sentence with zero filler; the operation and its ordering guarantee are stated immediately with nothing redundant.

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?

With an output schema present, return values need no explanation, and the annotations plus full schema coverage carry the safety and parameter burden. The remaining gap is minor: the description never indicates default filter behavior or that pagination is expected, though offset/limit are documented in the schema.

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% — every parameter (limit, since, state, offset, asset_id, severity) has its own schema-level documentation including enums and pagination semantics. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 and resource (list alarms) and adds the default ordering semantics ('most severe and most recent first'), which is genuinely informative. It does not explicitly name a sibling alternative, but no competing alarm-listing sibling exists, so ambiguity is low.

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?

The description gives no when-to-use guidance, no mention of the filtering options (state, severity, asset_id, since) an agent would need to decide between, and no reference to alternatives such as acknowledge_alarm. Usage is only inferred from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server