Skip to main content
Glama

List GitOps credentials

list_gitops_credentials
Read-only

List the git credentials available for GitOps integration: GitHub and Bitbucket Cloud, organisation and personal. Used during cluster creation to optionally connect a GitOps repository for GitOps-driven deployment of cloud components (hcloud CCM, CSI). Returns each credential's id, name, provider ('github' or 'bitbucket_cloud'), credential_scope and availability. A create names the credential by gitops_credential_name and takes its provider as gitops_provider. An organisation credential wins over a personal one of the same name, so a personal credential marked shadowed_by_organisation_credential cannot be chosen by name.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read, so the description's main added value is the undocumented return shape: id, name, provider values, credential_scope and availability, plus the shadowing rule. That helps because no output schema exists. Minor gaps are pagination and ordering, which are not mentioned.

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?

It is front-loaded: purpose first, then return fields, then constraints, which is the right order. It is dense and the paragraph about how a create names the credential is slightly off-scope for a list tool, costing a bit of tightness.

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 zero parameters, no output schema and a read-only annotation, the description carries the right load: it explains what is returned and the shadowing caveat that affects downstream selection. Only return-volume or pagination behavior is unstated, which is a small gap for a list endpoint.

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?

There are zero parameters, so the baseline is a 4. The description does introduce names like gitops_credential_name and gitops_provider, but these belong to the downstream create call, not to this tool's inputs, so they inform rather than clarify its own parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("List the git credentials available for GitOps integration") and narrows the scope precisely to GitHub and Bitbucket Cloud, organisation and personal. That is far more specific than sibling list tools such as list_credentials or list_helm_registry_credentials, so an agent can distinguish them without opening a schema.

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?

Usage context is explicit: "Used during cluster creation to optionally connect a GitOps repository for GitOps-driven deployment of cloud components (hcloud CCM, CSI)." That tells the agent when this tool matters. However, it never names the alternatives (list_credentials, list_provider_credentials) or excludes them, which is the only reason this is not a 5.

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.