Skip to main content
Glama

Get addon details

get_addon_details
Read-only

Get detailed information about a specific addon including version, sync status, health, and resource tree.

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_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
addon_nameYesName of the addon to get details for.
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 tells the agent this is a safe, non-mutating read, so the description's remaining job is to add context beyond that. It does add value by enumerating the returned facets (version, sync status, health, resource tree), which partially substitutes for the absent output schema, but says nothing about cost, latency, error behavior for unknown addon names, or whether the resource tree is large.

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?

One front-loaded sentence with no filler; the verb, scope, and returned fields all appear immediately. It is efficient, though the field enumeration could have been paired with a routing hint at the same length cost.

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?

With only two required parameters and no output schema, the description is adequate but thin: enumerating the returned fields is the right move given no output schema exists. What it omits is disambiguation from the many sibling addon-inspection tools, which is the main ambiguity an agent faces here.

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%: addon_name is self-explanatory and cluster_id already documents the UUID format and points to list_clusters for discovery. The description adds no further meaning about either parameter, 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?

States a specific verb and resource ("Get detailed information about a specific addon") and enumerates the payload (version, sync status, health, resource tree), which hints at how it differs from narrower siblings. However, it never names or contrasts with get_addon_status, get_addon_configuration, get_addon_settings, or get_addon_history, leaving the agent to infer the boundary in a crowded get_addon_* family.

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 explicit when-to-use guidance, no when-not-to-use, and no named alternative despite six sibling tools operating on the same addon resource. The agent must guess whether to call this or get_addon_status first, which is exactly the decision the description should settle.

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.