Skip to main content
Glama

ExducerAI GPU cloud

Saved SSH keys

list_ssh_keys
Read-onlyIdempotent

The SSH public keys saved on the account: a booking with no ssh_public_key uses them (not available to a sandbox key). Adding or removing keys is done by the user in the console.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower, yet the description adds genuinely new behavior: account-wide scope, the fallback relationship to bookings lacking an ssh_public_key, the sandbox exclusion, and that key management is console-only. It doesn't describe the returned fields or whether sandbox keys are listed at all, which is the main remaining gap.

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?

One sentence with the resource stated up front, followed by the operational caveats. The nested parenthetical ('not available to a sandbox key') is slightly awkward to parse but carries real information, so little is wasted.

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?

For a zero-argument read tool with no output schema, the description covers what is returned and the key caveats an agent needs to interpret the result. The only shortfall is that it doesn't indicate the shape of each returned key entry or whether an empty list vs. sandbox restriction is how the exclusion manifests.

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 nothing for the description to disambiguate; the baseline applies. The description correctly implies no scoping input is needed by framing the result as the account's full key set.

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 identifies the specific resource (SSH public keys saved on the account) and its scope (account-level, not sandbox-specific), which is enough for an agent to know what it retrieves. It doesn't explicitly name a sibling tool it contrasts with, though none of the listed siblings appear to return keys, so the risk of confusion is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives real usage context: keys are what a booking without an ssh_public_key falls back to, and they are not available to a sandbox key. It also rules out write usage by stating that adding or removing keys happens in the console, implicitly steering the agent away from expecting mutation here. It stops short of an explicit 'call this when X' instruction.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources