Skip to main content
Glama

Create chart service profile

create_chart_service_profile
Destructive

Make one Helm chart into a stack profile a managed-service package can be published over (the twin of ankra services packages init --addon), and publish the profile's first version. Name the chart, its version and the Helm registry it is registered under in Ankra (the organisation's own registry of that name, or the shared catalogue's); values_yaml is the chart's values. The profile is one stack holding the chart in each service's own namespace. With generated_secret (a Secret name and 1 to 16 keys, each random of 16 to 64 characters with length, default 32, or a fixed value such as a user or database name), the profile also generates that Secret in each service's namespace on its first install and keeps it unchanged across upgrades; Ankra never sees or stores the values. Point the chart at the Secret through its own existing-secret values in values_yaml, then name it as connection.secret_name in the package. Use get_service_profile_pin on the returned profile and version before publish_service_package. A refused request answers with the field that failed. A published profile version cannot change. Requires profiles.write.

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": {
      "name": "<name>",
      "chart_name": "<chart_name>",
      "chart_version": "<chart_version>",
      "registry_name": "<registry_name>"
    },
    "name": "create_chart_service_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe profile's name, a Kubernetes name (lowercase letters, digits and hyphens).
chart_nameYesThe Helm chart's name, which is also its release name: lowercase letters, digits and hyphens, at most 53.
descriptionNoOptional description of the profile.
values_yamlNoOptional values for the chart, as YAML, at most 256 KiB.
chart_versionYesThe chart version to pin.
registry_nameYesThe Helm registry the chart comes from, as named in Ankra.
generated_secretNoOptional Secret the profile generates for each service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the call publishes immediately, that a published profile version cannot change, that generated Secret values are never seen or stored by Ankra and remain unchanged across upgrades, that refusals return the failing field, and that `profiles.write` is required. That is substantial mutation, lifecycle, and auth context that the destructiveHint/idempotentHint flags alone do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main action is front-loaded, and most sentences carry needed facts, but the prose is one dense paragraph with deep nested parentheses — the `generated_secret` sentence is a long run-on that is hard to scan. Bullets or shorter sentences would preserve the information with far less reading effort.

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?

For a 7-parameter tool with a nested object, no output schema, and destructive semantics, the description covers the write path, the privilege needed, the immutability consequence, secret lifecycle, failure behaviour, and the required follow-up call. Only the shape of a successful response is left implicit (inferred from "the returned profile and version").

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%, so the baseline is 3, but the description adds real meaning: `registry_name` resolves to the organisation's own registry of that name or the shared catalogue's, `values_yaml` is the chart's own values, and `generated_secret` semantics (1–16 keys, 16–64 chars, default length 32, fixed-value alternative) are explained in operational terms. The Secret-to-package wiring guidance goes beyond anything the schema states.

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?

The description opens with a specific verb and resource — turning one Helm chart into a stack profile and publishing its first version — and adds the CLI equivalent (`ankra services packages init --addon`) plus the key distinguishing fact that the profile is one stack holding the chart in each service's own namespace. An agent can separate this from `create_stack_profile`, `create_stack_profile_draft`, and `publish_stack_profile_draft` without reading any schema.

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?

It gives clear downstream sequencing: use `get_service_profile_pin` on the returned profile and version before `publish_service_package`, and it explains how `generated_secret` must be wired into `values_yaml` and `connection.secret_name`. It does not explicitly say when to prefer `create_stack_profile` / `create_stack_profile_draft` instead, so exclusions are implied rather than stated.

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.