Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

get_alarms

Retrieve active system alarms from VergeOS virtualization platforms to monitor cluster health and identify operational issues.

Instructions

Get active system alarms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function for the get_alarms tool. Makes an authenticated API request to the VergeOS endpoint /api/v4/alarms?fields=most to retrieve active system alarms.
    async getAlarms() {
      return this.request("/api/v4/alarms?fields=most");
    }
  • Schema definition for the get_alarms tool, including name, description, and empty input schema (no parameters required). Part of the TOOLS array used for ListTools response.
      name: "get_alarms",
      description: "Get active system alarms",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.js:606-611 (registration)
    Tool registration and dispatch logic in the MCP CallToolRequestSchema handler. The switch case for "get_alarms" invokes the api.getAlarms() handler.
    case "get_logs":
      result = await api.getLogs(args?.limit || 50);
      break;
    case "get_alarms":
      result = await api.getAlarms();
      break;
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe important behavioral aspects like whether this returns real-time or historical data, pagination behavior, rate limits, authentication requirements, or what constitutes an 'active' alarm. The description is minimal and lacks operational context.

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?

The description is extremely concise at just three words, front-loading the essential information with zero wasted text. Every word earns its place, making it immediately clear what the tool does without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what format the alarms are returned in, what information they contain, whether this is a read-only operation, or any error conditions. Given the complexity of system monitoring and the lack of structured documentation, the description should provide more operational context.

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 has zero parameters with 100% schema description coverage, so the schema fully documents the parameter situation. The description doesn't need to compensate for any parameter gaps, and the baseline for zero parameters is 4. The description appropriately doesn't mention parameters since none exist.

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 'Get active system alarms' clearly states the verb ('Get') and resource ('active system alarms'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_logs' or 'get_cluster_status', but the specificity of 'alarms' provides inherent distinction.

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?

No guidance is provided on when to use this tool versus alternatives. While the description implies it's for retrieving alarm information, it doesn't specify whether this is for real-time monitoring, historical analysis, or how it differs from related tools like 'get_logs' or status-checking siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dvvincent/vergeos-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server