Skip to main content
Glama

SSH keys

list_ssh_keys
Read-onlyIdempotent

List SSH public keys on a GoMami account, with optional pagination controls for page number and results per page.

Instructions

List the SSH public keys on the account.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
resultsNoResults per page (default 20, max 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds only the word "public" and the account scope; it says nothing about pagination behaviour, whether an empty account returns an empty list or an error, or result ordering.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is close to under-specification rather than deliberate tightening.

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

Completeness3/5

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

For a two-optional-parameter read-only list tool with full schema coverage and complete annotations, the description is minimally sufficient. It omits pagination framing and result-shape expectations, which are the only things an agent would still need to reason about.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters (page, results) carry their own defaults and bounds, so the description does not need to restate them. It does not, however, add any nuance such as whether pagination is required to see all keys, leaving the schema to do all the work — the baseline 3 case.

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 ("List the SSH public keys") plus a scope ("on the account"), which is enough to separate it from siblings such as list_isos or list_servers by resource noun. It stops short of any explicit contrast with alternatives, but the resource name itself 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 statement of when to use this tool versus a get_* or verify_connection sibling, no prerequisites, and no guidance on how pagination should be driven when there are many keys. The only implied guidance is the generic read-list semantics carried by the tool name.

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