Skip to main content
Glama

List credentials

list_credentials
Read-only

List every credential in the organisation across all providers (git, helm, cloud providers, SSH keys, legacy aws/gcp) with identity, availability, and sync state. Secret values are never returned. Optional provider filter (e.g. 'github', 'hetzner', 'ssh-key'). A GitHub App credential also reports installation_id, which is what the related-repositories tools take. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
providerNoFilter to one provider: github, bitbucket_cloud, bitbucket_dc, helm, hetzner, ovh, upcloud, digitalocean, scaleway, proxmox, morpheus, azure, datasource, or ssh-key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Goes beyond readOnlyHint=true by disclosing what the response contains (identity, availability, sync state), what is deliberately excluded (secret values are never returned), and the installation_id field for GitHub App credentials. The trailing 'Read-only' merely restates the annotation, and there is no mention of ordering or volume limits despite the 'every credential' scope.

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?

Four compact sentences, front-loaded with scope, then return contents, then the optional filter, then the downstream hint. Only the final 'Read-only.' is wasted since the annotation already declares it.

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?

No output schema exists, so the description must characterize results, and it does: identity, availability, sync state, no secret values, plus installation_id for GitHub App creds. For a zero-required-parameter read-only list tool this is close to complete; only pagination/ordering behavior is unaddressed.

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 provider parameter already documents the full provider list, so the description's examples ('github', 'hetzner', 'ssh-key') mostly duplicate structured data. It does confirm the parameter is optional and that omitting it lists all providers, which is a small addition over the schema.

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 with an explicit scope: every credential in the organisation across all providers, enumerating git, helm, cloud providers, SSH keys and legacy aws/gcp. This implicitly separates it from the provider-scoped siblings (list_provider_credentials, list_gitops_credentials, list_helm_registry_credentials), though none is named outright.

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?

Usage is only implied by the 'list everything' framing; there is no explicit when-to-use versus get_credential or the provider-specific list tools. It does add one genuinely useful routing hint — that a GitHub App credential's installation_id is what the related-repositories tools consume — which points the agent toward a downstream call.

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.