Skip to main content
Glama

Get addon status

get_addon_status
Read-only

Get status of installed addons/applications in the cluster managed by Ankra.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_addon_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
addon_nameNoSpecific addon name to check. If not provided, returns all addons.
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

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe, non-mutating read, so the description need not restate safety. It does add mild scope information ('installed' addons, scoped to a specific cluster), but it never says what 'status' actually contains, whether results are live-queried from the cluster agent, or what happens if the cluster is unreachable.

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?

A single well-formed sentence with the resource and scope front-loaded and no filler. It is efficient, though the terseness contributes to the gaps in usage and behavioral detail rather than compensating for them.

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

Completeness3/5

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

This is a simple two-parameter read tool with full schema coverage and a readOnly annotation, so the structural burden is low. Still, with no output schema the description should hint at what a 'status' result looks like (health, version, sync state) or its granularity per-addon, and it does not.

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 the schema already explains both addon_name (optional, all addons if omitted) and cluster_id (UUID, discoverable via list_clusters). The description adds no additional parameter meaning, so the baseline 3 applies.

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 names a specific verb and resource ('Get status of installed addons/applications') and scopes it to a cluster managed by Ankra, so the basic operation is unambiguous. However, it gives no differentiation from close siblings such as get_addon_details, get_addon_configuration, list_addons, or get_cluster_addon_security, leaving the agent to guess which one returns 'status'.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no named alternative. The definition never explains why an agent would pick this over get_addon_details or list_addons, and the only routing hint ('Discover ids with list_clusters') lives in the schema, not the description.

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.