Skip to main content
Glama

Deploy finalize analysis

deploy_finalize_analysis
Read-only

TERMINATOR tool: call this exactly once at the end of your analysis with the full DeployAnalysis payload. The server validates against the Pydantic schema and rejects any malformed analysis (you'll get an error message and should call again with corrections). Returns severity 'ok' on success, after which you should end your turn.

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": {
      "analysis": "<analysis>",
      "cluster_id": "<cluster_id>"
    },
    "name": "deploy_finalize_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
analysisYesFull DeployAnalysis JSON: needs_ingress (bool), service_port (int|null), needs_database ('postgres'|'mysql'|'redis'|null), required_secrets ([{name, key, hint?}]), required_env ([{name, hint?, secret_ref?}]), chart_values_shape ({ingress_enabled_path, ingress_host_path, ingress_class_path, env_path, env_from_path, image_repository_path; each str|null}), summary (str|null).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real behavioral context the annotation cannot: server-side Pydantic validation, rejection with an error message, a retry-on-error loop, and the success signal ('severity ok') with an end-turn instruction. It does not say what the server does with the accepted analysis (persist it, hand off to a deploy, etc.), which is the one remaining behavioral gap.

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 terminator/exactly-once constraint, then validation behavior, then the success-and-stop instruction. No filler; slightly dense but every clause carries operational meaning.

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?

Covers calling frequency, validation, error recovery, return signal, and post-call behavior for a two-parameter terminal tool with a large nested payload and no output schema. What the server ultimately does with the accepted analysis is left implicit, but the agent has enough to call correctly.

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%; both the top-level params and the entire nested analysis object are documented in the schema, including the chart_values_shape fields. The description only repeats 'full DeployAnalysis payload' without adding format, ordering, or completeness hints beyond the schema.

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 action (submit the full DeployAnalysis payload as the terminal step of the analysis) and marks itself as the TERMINATOR tool, which cleanly distinguishes it from the deploy_inspect_* siblings it sits among. An agent knows exactly what this tool is for without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when ('at the end of your analysis'), how often ('exactly once'), and what to do on failure ('you'll get an error message and should call again with corrections'), plus the post-call instruction to end the turn. The only missing piece is naming a sibling alternative, but none exists — this is a terminal step.

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.