Skip to main content
Glama
Sign In
aeza-mcp

aeza-mcp

by rdydygin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

services_ssh_keys_get_list

Read-onlyIdempotent

Retrieve a paginated list of SSH keys from Aeza, with sorting, filtering, limit, and offset options for managing server access.

Instructions

Get SSH keys list GET /services/ssh-keys

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_ssh_keys_get_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
filterNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/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 adds only the raw endpoint path and nothing about pagination defaults, result ordering, or what the response contains — essentially no behavioral value beyond the annotations.

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 with no filler, and the purpose is front-loaded before the endpoint. It is efficient, though the terseness comes at the cost of any useful detail.

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?

With no output schema, four undocumented query parameters, and no explanation of pagination or filtering behavior, the definition is under-specified for a paginated list endpoint. An agent knows what it returns at a high level but not how to page or filter correctly.

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

Parameters2/5

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

All four parameters (sort, limit, filter, offset) have 0% schema description coverage, so the description carries the full burden and provides nothing — no syntax for 'sort' or 'filter', no statement that limit defaults to 50 and offset to 0, no maximums. The only hints are parameter names themselves.

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 states a specific verb and resource ('Get SSH keys list') plus the underlying endpoint 'GET /services/ssh-keys', which makes clear it returns a collection of SSH keys rather than a single key. It does not explicitly contrast with the singular 'services_ssh_keys_get' sibling, but the plural resource is unambiguous.

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 list tool versus 'services_ssh_keys_get' or the other *_get_list siblings, and no mention of prerequisites such as required scopes or whether the list is scoped to the authenticated account. The agent must infer all of this.

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