Skip to main content
Glama

List available charts

list_available_charts
Read-only

Browse the Helm chart catalog. Use to verify a specific chart exists or to show the user what's available. Do NOT pass these results as bulk requirements to design_stack - only pass the specific charts the user requested.

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": "list_available_charts"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoSearch term to filter charts by name or description.
categoryNoFilter charts by category (e.g., 'monitoring', 'security', 'database').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuine behavioral context beyond that: results are a browsing artifact and should not be passed wholesale into a design step. However, it says nothing about result size, pagination, or whether the catalog is scoped to configured registries.

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 action and followed by usage and a caution; nothing is padded. The reference to `design_stack` is slightly awkward because no such sibling appears in the available tool list, which may cost the agent a moment of lookup.

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 optional parameters and no output schema, the definition is close to sufficient, but it never says what a listing entry contains (name only, description, category, versions) or how many results to expect. For a discovery tool whose output drives downstream chart selection, that gap is worth flagging.

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%, so both `search` and `category` are already documented in the schema with their filtering semantics. The description adds no further meaning such as matching behavior, case sensitivity, or whether filters combine with AND. Baseline 3 applies since the schema carries the parameter burden.

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?

"Browse the Helm chart catalog" gives a specific verb and resource, and the follow-up clause clarifies the two concrete use cases (existence check, catalog discovery). It does not name the adjacent catalog tools (get_chart_details, list_chart_versions, get_chart_default_values), so an agent must infer the boundary from the catalog of sibling names alone.

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 when-to-use is stated: verify a specific chart exists, or show the user what's available. It also carries a clear negative instruction against bulk-forwarding results. What's missing is routing to the sibling that should be used when the user wants details or versions rather than a listing.

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.