Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Keypair List

get_keypair_list

Retrieve a list of SSH keypairs for the current user, including key types, fingerprints, creation dates, and truncated public key info for security key management queries.

Instructions

Get list of SSH keypairs for the current user.

Functions:

  • Query SSH keypairs and their fingerprints

  • Display keypair types and creation dates

  • Show public key information (truncated for security)

  • Provide keypair management information

Use when user requests SSH key management, keypair information, or security key queries.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add real behavioral context beyond the name: results are scoped to the current user, and public keys are truncated for security, implicitly indicating private key material is not returned. It says nothing about permissions required, result ordering, or whether the list is paginated.

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 purpose and the usage trigger are front-loaded and readable, but the intervening four-bullet 'Functions' block is padded: 'Provide keypair management information' is vague filler, and 'Query SSH keypairs and their fingerprints' repeats the opening sentence. The bullet list could be compressed to one line without losing information.

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?

An output schema exists, so the description need not enumerate return fields, and it does not. For a zero-parameter, read-only listing tool the remaining essentials — what it returns, whose data, and when to reach for it — are all present, with only permission/pagination details missing.

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 takes zero parameters, so there is no parameter semantics for the description to compensate for. The baseline of 4 applies; the description correctly does not invent arguments and notes the implicit current-user scoping that a reader might otherwise expect to be a filter.

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 first sentence names a specific verb and resource (list SSH keypairs) and scopes it to the current user, which is enough for an agent to distinguish it from the surrounding image/load-balancer/volume listing siblings. It stops short of any explicit differentiation from other identity-type tools, so it is clear but not maximally so.

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?

The closing line gives a usage trigger (SSH key management, keypair information, security key queries), but it largely restates the purpose already stated in sentence one. There are no exclusions, no prerequisites, and no named alternatives for cases where the agent wants another user's keypairs or a single keypair's details.

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