Skip to main content
Glama
Sign In
aeza-mcp

aeza-mcp

by rdydygin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

services_operating_systems_get_list

Read-onlyIdempotent

Retrieve a paginated list of available service operating systems, filtered and sorted as needed, to select the right OS for server provisioning.

Instructions

Services operating systems get list GET /services/operating-systems

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

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
filterNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

D1.9/5.0
Behavior2/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 fully covered by structured data. The description contributes nothing further: no mention of pagination behavior, default page size, sort/filter syntax, rate limits, or what a result entry contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The definition is very short and front-loaded with the resource and endpoint path, with no filler. However, its brevity reflects under-specification rather than disciplined editing — there is essentially no substantive content to trim.

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

Completeness1/5

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

For a four-parameter paginated list endpoint with no output schema and no parameter documentation, the description leaves critical gaps: filter syntax, sortable fields, pagination semantics, and the shape of returned items. An agent could call it only by guessing.

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% across four parameters (sort, limit, filter, offset), and the description supplies no compensating meaning. An agent cannot learn from the definition what values 'sort' accepts, what syntax 'filter' takes, or how limit/offset interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name ("Services operating systems get list") and appends the HTTP route "GET /services/operating-systems". It conveys that a collection of operating systems is retrieved, but adds no verb-level specificity or scope detail beyond what the name already encodes.

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 statement of when to use this tool, when not to, or how it differs from related list endpoints such as services_get_list or services_operating_systems_get_recipes_list. The agent must infer usage entirely from the name.

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