Skip to main content
Glama

Get credential

get_credential
Read-only

Get one credential's details by id: identity, provider, availability, and the clusters and running operations depending on it. Every secret-bearing field (tokens, keys) is redacted; the response marks secret_values_redacted. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "credential_id": "<credential_id>"
    },
    "name": "get_credential"
  }
}

Input Schema

NameRequiredDescriptionDefault
credential_idYesUUID of the credential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses that secret-bearing fields such as tokens and keys are redacted and that the response marks secret_values_redacted. It also names the non-secret details returned, though it does not cover permissions, error behavior, or rate limits.

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?

The description is front-loaded with the action and resource, then explains returned data and redaction. The final 'Read-only' slightly repeats the readOnlyHint annotation, but otherwise there is little unnecessary 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?

For a one-parameter read-only tool with no output schema, the description is sufficiently complete about what is returned and how secrets are handled. It omits error/not-found behavior and permission requirements, leaving a small gap.

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 schema already defines credential_id as a UUID. The description only reiterates that lookup is by id and adds no format, source, or validation nuance beyond 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: get one credential by id, with returned facets such as identity, provider, availability, and dependent clusters/operations. The 'one credential' scoping implicitly contrasts with list_credentials, but no sibling is named explicitly.

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?

The phrase 'by id' implies this is for when a credential UUID is already known, and 'Read-only' clarifies the operation type. However, it gives no explicit when-to-use guidance versus list_credentials, get_github_credential_usages, verify_github_credential, or related credential 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.