Skip to main content
Glama

vspc_list_alarms

Read-onlyIdempotent

List active VSPC alarms across all clients, newest first, with status, time, message, object, computer, and company details. Filter by hours, company, or status; defaults to Error and Warning alarms.

Instructions

Triggered (active) VSPC alarms across every client, newest first: alarm name, status (Error, Warning, ...), time, message, the object (job, server, agent, repository...), computer and company. Defaults to Error and Warning alarms.

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

Input Schema

NameRequiredDescriptionDefault
hoursNoOnly alarms last triggered within this many hours.
limitNoPage size (VSPC maximum 500).
offsetNoItems to skip (for the next page).
companyNoCompany (client) as its VSPC UID or its name (exact, or a unique part of it). Leave out for every company.
statusesNoAlarm statuses to include (default Error and Warning).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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/openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the result ordering ('newest first'), the default status filter (Error and Warning), and the fact that it spans every client with no tenant scoping.

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 the key scope and ordering first, followed by a compact colon list of returned fields and the default filter. No filler or redundant phrasing.

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 no output schema, the description usefully enumerates the returned fields (name, status, time, message, object, computer, company) and states the ordering and defaults. Pagination and per-parameter semantics are handled by the schema, so the only real omission is any note on result volume or how to reach non-default statuses.

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%, so hours, limit, offset, company and statuses are all documented in the schema itself. The description only restates the status default and the all-company default, adding little semantic meaning beyond what the structured fields already provide; 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?

The description names the resource and its state ('Triggered (active) VSPC alarms'), the scope ('across every client'), the ordering ('newest first'), and enumerates the returned fields. That is enough to distinguish it from write-side siblings like vspc_acknowledge_alarm and vspc_resolve_alarm, though it never explicitly contrasts itself with a sibling by name.

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: 'across every client' and 'Defaults to Error and Warning alarms' tell the agent the default scope and filter, but there is no explicit when-to-use guidance, no exclusion (e.g. how to see acknowledged/resolved alarms other than via the statuses param), and no pointer to alternatives.

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