Skip to main content
Glama

Get addon definitions

get_addon_definitions
Read-only

Read the organisation's add-on definitions (the twin of ankra helm addon-catalog list and get): each names an add-on and matches Helm charts to it by chart name, keyword or home URL; source global is Ankra's and read-only, source org is the organisation's own. Without definition_name it lists them; with it, it returns that definition with its manual chart links. Read-only; creating, changing and deleting a definition or a chart link are not offered here.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_addon_definitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
definition_nameNoOne definition's name (its slug).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description then adds non-obvious context the annotations cannot carry: the 'source global' entries are Ankra's own and read-only while 'source org' entries belong to the organisation. It also clarifies the return shape in each mode and that mutation is unavailable here, though it says nothing about volume, pagination, or what happens when definition_name does not match.

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?

Information is front-loaded: the resource, then the matching model, then the mode switch, then the exclusion. The parenthetical CLI twin reference and the source/ownership aside add useful context but make the first sentence long and slightly harder to scan; nothing is fully redundant, though the CLI mapping could be trimmed.

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 burden of describing return values and does so for both modes (a list of definitions vs one definition plus its manual chart links). Missing are error/empty-case behavior and any hint of result size or filtering, which matter for a catalog-style read but are secondary to correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (the single parameter is documented as 'One definition's name (its slug)'), so a baseline of 3 applies. The description earns above baseline by tying the parameter to a distinct behavior: supplying it switches the tool from a listing to a single-definition fetch that includes that definition's manual chart links.

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?

States a specific verb and resource ('Read the organisation's add-on definitions') and then explains the domain model: definitions map Helm charts by chart name, keyword or home URL, with a global (Ankra-owned, read-only) vs org (own) source distinction. It also resolves the list-vs-single ambiguity of the name by spelling out what happens with and without definition_name.

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?

Explicit mode selection is given ('Without definition_name it lists them; with it, it returns that definition with its manual chart links'), and the exclusion is stated outright ('creating, changing and deleting a definition or a chart link are not offered here'). The gap is that the alternatives named are CLI commands ('ankra helm addon-catalog list' and 'get') rather than MCP siblings, so an agent cannot tell this apart from get_addon_details or get_addon_configuration from the text alone.

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.