Skip to main content
Glama

Add Helm registry

add_helm_registry
Destructive

Add a Helm chart registry to the organisation's catalog. After adding, the registry will be indexed and its charts will become available for stack design. Use this when the user needs charts from a registry that isn't in the catalog yet (e.g., 'Add the Istio Helm registry at https://istio-release.storage.googleapis.com/charts').

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": {
      "registry_name": "<registry_name>",
      "registry_url": "<registry_url>"
    },
    "name": "add_helm_registry"
  }
}

Input Schema

NameRequiredDescriptionDefault
registry_urlYesURL of the Helm chart repository (e.g., 'https://istio-release.storage.googleapis.com/charts').
registry_nameYesName for the registry (e.g., 'istio', 'bitnami'). Must be lowercase alphanumeric with hyphens.
registry_typeNoRegistry type. Use 'http' for standard Helm repos, 'oci' for OCI-based registries.http

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true. The description adds a genuine post-condition the annotations cannot convey: the registry is indexed and its charts become usable for stack design. However, it does not explain why a non-idempotent, destructive-flagged tool behaves that way, what happens on duplicate names, what permissions are needed, or how registry indexing completes.

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?

Two sentences plus an illustrative example, with the purpose and catalog constraint front-loaded before the usage trigger. The quoted example URL duplicates the schema's own example, which is mildly redundant, but it earns its place by showing the user-facing phrasing that should trigger the tool.

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 small three-parameter creation tool with full schema coverage and no output schema, the description covers purpose, trigger condition and the downstream indexing effect. Gaps remain around failure/duplicate behavior and permission prerequisites, both relevant given the non-idempotent, destructive annotation profile.

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%, so registry_name, registry_url and registry_type (with its http/oci enum and default) are already fully documented in the schema. The description only echoes a URL value inside its usage example and adds no new meaning about naming rules or when to prefer 'oci' over 'http'.

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?

The description opens with a specific verb+resource ('Add a Helm chart registry to the organisation's catalog') and immediately scopes it to a registry 'that isn't in the catalog yet', which implicitly separates it from list_helm_registries, get_helm_registry and sync_helm_registry. It stops short of naming a sibling as an alternative, so differentiation is inferable rather than explicit.

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?

It gives an explicit when-to-use condition ('when the user needs charts from a registry that isn't in the catalog yet') and reinforces it with a concrete user-style example. It never states the inverse case – what to do when the registry already exists (e.g., sync instead of add) – so the guidance is clear but has no exclusions.

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.