Skip to main content
Glama

List Helm registries

list_helm_registries
Read-only

The organisation's connected Helm chart registries (the twin of ankra helm registries list): name, URL, kind (HTTP or OCI), credential name, sync state and chart counts. Registry credentials are never returned. Use this to answer where a chart comes from or whether a private registry is connected; add_helm_registry connects a new one. 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_helm_registries"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
searchNoFilter registries by name.
page_sizeNoRows per page (default 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it while adding genuinely new behavior: which fields are returned and the guarantee that 'Registry credentials are never returned' — an important disclosure that shapes follow-up tool selection toward list_helm_registry_credentials. It does not mention pagination or result ordering, and with no output schema the listing of returned fields carries useful load.

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?

Well front-loaded: the resource and returned fields come first, then the use case, then the alternative, then the read-only note. The CLI equivalence parenthetical ('the twin of `ankra helm registries list`') is useful grounding for some agents but is the one clause that could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with no output schema, the description supplies what the schema cannot: the returned field set, the credential redaction guarantee, and the pairing with add_helm_registry. Nothing an agent needs in order to call this correctly is missing.

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 description coverage is 100% and all three parameters (page, search, page_size) are documented inline with defaults and bounds, so the schema does the heavy lifting. The description adds nothing about filtering or paging semantics, which is the expected baseline for fully covered schemas.

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 ('The organisation's connected Helm chart registries') and enumerates the returned fields (name, URL, kind HTTP/OCI, credential name, sync state, chart counts), which lets an agent separate it from list_helm_registry_credentials, get_helm_registry and sync_helm_registry 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?

Explicit usage context is given: 'Use this to answer where a chart comes from or whether a private registry is connected', plus a named sibling for the write path ('add_helm_registry connects a new one'). It stops short of naming when to prefer get_helm_registry for a single registry or list_helm_registry_credentials for auth details, so no explicit exclusion is drawn.

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.