listPrivateKeysList all SSH private keys to manage credentials used for server authentication and deploy keys. Use offset and limit to page through available keys.
List all SSH private keys. Keys are used for server authentication and deploy keys.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No |
Changes observed during successful MCP inspections.
v0.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, covering that this is a read operation. The description adds context about key usage but does not disclose pagination behavior (despite limit/offset params) or whether the response exposes sensitive key material. It provides some value but lacks richer behavioral detail beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, front-loaded with the action, and includes only relevant context. Every word earns its place with no unnecessary information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool, the description gives a clear purpose but omits important details: it claims to list 'all' keys yet has limit/offset parameters, suggesting pagination that is not mentioned. Without an output schema, it also fails to describe the return format. Gaps exist, but the tool's simplicity and annotations keep it adequate overall.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has two parameters (limit, offset) with no descriptions, and schema coverage is 0%. The description does not mention pagination or how these parameters affect results, so it fails to compensate for the missing schema details, leaving parameters entirely unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'List all SSH private keys' with a specific verb and resource. It also adds context that keys are used for server authentication and deploy keys, which distinguishes this list operation from sibling tools like createPrivateKey, getPrivateKey, updatePrivateKey, and deletePrivateKey.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description makes clear it should be used to list all SSH private keys, providing explicit context. However, it does not mention alternatives like getPrivateKey for individual keys or specify when not to use this tool, so it stops short of full guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.