Skip to main content
Glama

List provider credentials

list_provider_credentials
Read-only

List cloud provider credentials and SSH key credentials available in the user's organisation. Use this before creating a cluster to find the credential_id (cloud API token) and ssh_key_credential_id needed for provisioning. Filter by provider to narrow results.

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

Input Schema

NameRequiredDescriptionDefault
providerNoFilter by provider type. Use 'ssh-key' to list SSH key credentials shared across providers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful context beyond that: results are scoped to the user's organisation and the returned IDs feed cluster provisioning. It says nothing about pagination, ordering, or what happens when no credentials exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource and followed by the actionable purpose and filter hint. No redundant or filler wording.

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?

With no output schema, the description usefully names the key returned fields (credential_id, ssh_key_credential_id) an agent needs downstream. For a single optional-parameter read tool this is nearly complete; only return-shape details like pagination are absent.

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 coverage is 100% and the enum values are documented in the schema, including the 'ssh-key' special case. The description only restates that provider narrows results, adding no format or defaulting detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('List cloud provider credentials and SSH key credentials') and scopes it to the user's organisation, which implicitly separates it from list_gitops_credentials and list_helm_registry_credentials. It does not explicitly name the closest sibling, list_credentials, so an agent must infer the boundary.

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?

Gives a concrete when-to-use: call it before creating a cluster to obtain credential_id and ssh_key_credential_id. It also explains the filter's purpose. It stops short of stating when not to use it or naming the alternative credential-listing tools.

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.