Skip to main content
Glama

Get chart details

get_chart_details
Read-only

Detailed information about a Helm chart at a repository URL (the twin of ankra charts info): description, maintainers, home, sources, versions and the app version each carries. 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": {
      "chart_name": "<chart_name>",
      "repository_url": "<repository_url>"
    },
    "name": "get_chart_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
chart_nameYesThe chart's name.
repository_urlYesThe chart repository URL (from list_available_charts or list_helm_registries).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The 'Read-only' note merely restates readOnlyHint=true already present in annotations. The description does add useful payload context by enumerating returned fields including per-version app versions, but says nothing about failure modes (missing chart, unreachable URL) or that this reaches out over the network to a repository.

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 dense, front-loaded sentence: purpose first, then returned fields, then the read-only note. The parenthetical CLI twin is a minor flourish but does orient users of the CLI; otherwise there is no waste.

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 return-value burden and does so by naming the fields returned. For a simple two-parameter read tool that is close to sufficient; only error/behavioral details are missing.

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 coverage is 100%, so both chart_name and repository_url are already documented, including the hint that repository_url comes from list_available_charts or list_helm_registries. The description only echoes the URL scoping ('at a repository URL') and adds no new parameter meaning.

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?

Names a specific verb+resource ('Detailed information about a Helm chart at a repository URL') and enumerates exactly what comes back: description, maintainers, home, sources, versions, and per-version app version. It does not explicitly contrast with near siblings such as list_chart_versions or get_chart_default_values, so the agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the mention of returned versions hints this subsumes a version listing, and the CLI twin reference ('ankra charts info') sketches the context. There is no explicit when-to-use or when-not-to-use guidance and no named alternative tool.

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.