Skip to main content
Glama

Add manifest to stack profile draft

add_manifest_to_stack_profile_draft
Destructive

Add a raw Kubernetes manifest to a stack profile builder draft (e.g. a Namespace, ConfigMap, or Secret scaffold). For Secret manifests, set every data/stringData value to the literal string ANKRA_SECRET_PARAMETER - real secret values are rejected.

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": {
      "manifest_name": "<manifest_name>",
      "manifest_yaml": "<manifest_yaml>"
    },
    "name": "add_manifest_to_stack_profile_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentsNoNames of draft resources this manifest depends on (deploy-order parents).
draft_idNoUUID of the stack profile builder draft. Defaults to the draft from the current page context, or the organisation's only open draft.
manifest_nameYesName for the manifest resource in the draft.
manifest_yamlYesThe manifest content as YAML (multi-document allowed).

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?

The annotations already declare destructiveHint=true, non-idempotent, and not readOnly, so the safety profile is covered. The description adds a genuinely non-obvious behavioral rule - real secret values are rejected and placeholders must be the literal ANKRA_SECRET_PARAMETER - but it never explains what makes the operation destructive, whether repeat adds create duplicate manifests, or how failures surface.

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?

Two sentences, front-loaded with the core action and tightened by the Secret caveat, with no filler. The parenthetical examples earn their place by clarifying the expected manifest scope.

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 draft-mutation tool with full schema coverage and annotations that already flag destructiveness, the definition covers purpose and the main content trap (secret placeholders). The remaining gap is the untold outcome - what the draft looks like after adding, and duplicate-handling - which matters for a non-idempotent write with no output schema.

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 description coverage is 100%, so the baseline is 3, but the description adds real constraint meaning for manifest_yaml: its content must use ANKRA_SECRET_PARAMETER placeholders for Secret data/stringData values or the call is rejected. That is a substantive content rule not present in the schema, though parents and draft_id semantics are left entirely to the schema.

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?

The description states a specific verb and resource ('Add a raw Kubernetes manifest to a stack profile builder draft') and clarifies the kind of content with examples (Namespace, ConfigMap, Secret scaffold). This clearly separates it from add_addon_to_stack_profile_draft by content type, though it never explicitly names apply_manifest or add_addon as the alternatives, so the contrast is implicit rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no comparison to apply_manifest, which is the most plausible lookalike sibling. The only usage direction is an in-content rule for Secret manifests, which is useful but is a 'how' rather than a 'when', leaving the selection decision to inference from the tool name.

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.