Skip to main content
Glama

Get addon settings

get_addon_settings
Read-only

Get an installed addon's operational settings on the cluster: sync policy, sync window, retry policy, ignore-differences rules, revision history limit, strict health check, rollback-on-failure, and keep-failed-resources-for-debug. 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_settings"
  }
}

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

A4.5/5.0
Behavior5/5

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

Since no output schema is provided, the description is vital for behavioral transparency. It discloses the exact list of configuration parameters returned, which defines the tool's output structure and ensures the AI agent knows precisely what data to expect upon successful execution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is extremely concise, using a single, information-rich sentence. The core function and all critical context (the settings list) are front-loaded and easily digestible.

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?

Given that this is a read-only tool without an output schema, describing the contents of the settings list is the maximum amount of contextual information available. This makes the definition fully complete for an agent attempting to use the tool correctly.

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?

With a 100% schema description coverage, the schema already details the input parameters (addon_name and cluster_id). The description adds no meaningful semantic meaning to these inputs, so the baseline score is appropriate.

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 clearly identifies the resource (an addon's operational settings) and provides a detailed list of what that resource includes (sync policy, retry policy, etc.). This distinguishes it from similar tools like get_addon_details or update_addon_configuration.

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?

While it doesn't list explicit 'use-if' statements, the exhaustive list of specific operational parameters (e.g., revision history limit) strongly defines the precise context in which this tool should be used, making it clear when this tool is required over a general status check.

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.