Skip to main content
Glama
Sign In
aeza-mcp

aeza-mcp

by rdydygin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

system_get_list

Read-onlyIdempotent

Retrieve active system alerts for specified slots to monitor server health and respond to issues.

Instructions

Get active system alerts by slots GET /system/alerts

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slots": "<slots>"
    },
    "name": "system_get_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/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 openWorldHint, so the safety profile is covered. The description contributes the 'active' filtering semantics and the REST endpoint, but says nothing about pagination, result volume, or what an empty result means.

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 short lines, front-loaded with the action and resource, with no filler. The raw endpoint line is marginally useful for context but borders on noise for an agent.

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 exactly one required parameter and no output schema, the definition should fully explain that parameter; instead 'slots' is left opaque. An agent cannot construct a correct call from this definition without guessing the slots format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the only required parameter, 'slots', is completely undefined — no format, delimiter, type of identifier, or example. The description's 'by slots' merely restates the parameter name and adds no meaning an agent could act on.

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 gives a specific verb and resource ('Get active system alerts') plus the underlying endpoint, which tells an agent what the call returns. The phrase 'by slots' is vague and the tool name (system_get_list) points at a generic 'systems' listing rather than alerts, so there is a slight name/description mismatch the agent must reconcile.

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?

There is no guidance on when to use this tool versus other list tools, no mention of prerequisites or exclusions, and no indication of what 'active' means relative to any non-active variant. The endpoint line implies usage but does not state it.

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