Skip to main content
Glama

Get addon configuration

get_addon_configuration
Read-only

Get an installed addon's configuration: its helm values document, chart metadata, and the latest apply operation. Secret values inside the configuration are redacted before they reach you. 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": {
      "addon_name": "<addon_name>",
      "cluster_id": "<cluster_id>"
    },
    "name": "get_addon_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
addon_nameYesName of the installed addon.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

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?

Annotations already declare readOnlyHint=true, so the closing 'Read-only' adds nothing, but the description does contribute real behavioral context beyond annotations: secret values are redacted before the data reaches the agent. That tells the caller not to expect usable credentials here and to route to request_secret/get_secrets instead. It stops short of noting anything about payload size or whether the helm values arrive as a string versus a parsed document.

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?

Three short sentences, front-loaded with the verb and the returned fields before the qualifiers. The trailing 'Read-only.' is redundant with the readOnlyHint annotation and is the only clause that does not earn its place.

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 return-value burden and does so adequately by naming the three components returned. For a two-parameter read tool with full schema coverage that is largely sufficient; only the shape of the helm values payload and the behavior when the addon is absent are unaddressed.

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 both parameters are documented there, including the pointer to list_clusters for discovering cluster_id. The description adds no meaning about the parameters themselves, so this sits at the baseline for schema-documented tools.

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+resource (get an installed addon's configuration) and enumerates the payload: helm values document, chart metadata, and the latest apply operation. That is enough to distinguish it from write-side siblings like update_addon_configuration, but it never clarifies how it differs from the crowded read-side cluster (get_addon_details, get_addon_settings, get_addon_status).

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?

Usage is only implied by the returned-contents list: an agent can infer you call this when you need helm values or chart metadata for an installed addon. There is no explicit when-to-use statement, no exclusion against the four near-identical get_addon_* siblings, and no note that the addon must already be installed (only the adjective 'installed' hints at it).

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.