Skip to main content
Glama

List alert ingest credentials

list_alert_ingest_credentials
Read-only

List the organisation's alert ingest credentials: what an external Alertmanager delivers alerts into Ankra with (the twin of ankra alerts ingest-credentials list). Each carries its name, scope (cluster, platform or mixed), whether it is enabled, the cluster it is pinned to and whether that cluster is gone, and when it was last used. A token is never listed: it is shown once, when the credential is created. Use it to answer why an external alert did not arrive (a disabled credential, one never used, one pinned to a cluster that no longer exists). Read-only; creating, rebinding and deleting a credential are not offered here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only carry readOnlyHint=true, and the description reinforces that with 'Read-only' while adding genuinely new context: which fields each record returns, that a pinned cluster may be reported as gone, and critically that the token itself is never listed because it is shown once at creation. That secret-handling disclosure is valuable and non-obvious. It stops short of describing ordering or result limits, so it is not exhaustive.

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?

Purpose is front-loaded in the first clause, followed by the returned fields and then the diagnostic use case – a sensible order. The parenthetical list of returned attributes is dense but each item is discriminative; only the CLI-equivalence aside feels expendable.

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 carries the burden of describing return values, and it does so by naming the per-record fields including the 'cluster is gone' state. For a zero-parameter read tool this is close to complete; only ordering, pagination or org-scoping mechanics are left unstated.

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 the baseline is 4 and there is nothing for the description to disambiguate. The description correctly implies an unfiltered listing of the organisation's credentials without inventing parameters that do not exist.

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?

States a specific verb and resource ('List the organisation's alert ingest credentials') and immediately explains the resource in domain terms: what an external Alertmanager delivers into Ankra. It also delimits the tool by naming the CLI twin and by declaring that creating, rebinding and deleting are not offered here, which separates it from the mutation siblings.

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

Usage Guidelines5/5

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

Gives an explicit diagnostic use case ('answer why an external alert did not arrive') and enumerates the failure conditions that make it the right call: disabled credential, never used, or pinned to a cluster that no longer exists. It also states the negative case up front – the create/rebind/delete operations are not available here – so the agent knows not to look for them in this tool.

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.