Control Plane

Get Installed Templates

get_installed_template

Read-onlyIdempotent

Show an installed release’s current status, revision, and the Control Plane resources it created (kind, name, link); without name, list the releases installed in the org (name, template, version, GVC, revision). Pass waitSeconds with name to wait on the server until the release is deployed and every workload it created is ready. Returns release metadata only: install values and manifests are never included. Reading a release requires the token to have reveal permission on its helm bookkeeping secret, where release state is stored.

Input Schema

Name	Required	Description
`org`	No	Organization slug.
`name`	No	Release name. Omit to list the releases installed in the org.
`waitSeconds`	No	Seconds to wait on the server until the release is deployed and every workload it created is ready, 0 to 45. The call returns as soon as it is, or with the latest state when the time runs out. Use this instead of calling again and again.

Output Schema

Name	Required	Description
`ok`	Yes
`data`	No	The full result. Read this, not only the summary.
`details`	No
`summary`	Yes
`nextSteps`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / name / description

Previous value: -"Release name — the unique, immutable identifier for this installed instance within the org."New value: +"Release name. Omit to list the releases installed in the org."

removedInput schema / required
```
Removed value: -[
-  "name"
-]
```

Changed18 schema fields changedSep 30, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / name / maxLength
```
Removed value: -63
```
removedInput schema / properties / name / minLength
```
Removed value: -1
```

removedInput schema / properties / name / pattern

Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"

changedInput schema / properties / org / description

Previous value: -"Organization slug (lowercase kebab-case). NEVER guess — if the user has not named one, ask. On org-not-found, stop and ask; do not retry variants."New value: +"Organization slug."

removedInput schema / properties / org / maxLength
```
Removed value: -63
```
removedInput schema / properties / org / minLength
```
Removed value: -1
```

removedInput schema / properties / org / pattern

Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"

addedInput schema / properties / waitSeconds

Added value: +{
+  "description": "Seconds to wait on the server until the release is deployed and every workload it created is ready, 0 to 45. The call returns as soon as it is, or with the latest state when the time runs out. Use this instead of calling again and again.",
+  "maximum": 45,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / required

Previous value: -[
-  "org",
-  "name"
-]New value: +[
+  "name"
+]

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / data / description

Previous value: -"The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary."New value: +"The full result. Read this, not only the summary."

addedOutput schema / properties / details
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / nextSteps / description

Removed value: -"Recommended follow-up actions for this task, in order."

removedOutput schema / properties / ok / description
```
Removed value: -"Whether the call succeeded."
```
removedOutput schema / properties / summary / description
```
Removed value: -"One-line summary of the result."
```

First observedJun 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the readOnly/idempotent annotations: it discloses that install values and manifests are never returned, that reads require `reveal` permission on the helm bookkeeping secret, and that waitSeconds blocks server-side until workloads are ready or the timeout expires. These are exactly the auth and scope facts an agent needs before calling.

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?

Front-loads the primary action and response fields, then handles the list mode, the wait behavior, and the permission caveat in order. It is dense as a single paragraph, but every sentence carries distinct information with no restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite a modest three-parameter schema, the description covers both invocation modes, expected response fields, the permission prerequisite, and the exclusion of sensitive payloads. With an output schema present, nothing an agent needs to call this correctly is missing.

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 baseline is 3, but the description adds a constraint the schema does not: waitSeconds is only meaningful when passed with `name`, and `name`'s absence switches the whole response shape to a list. That mode-switching semantics adds real value beyond the field docs.

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?

Opens with a specific verb and resource ('Show an installed release's current status, revision, and the Control Plane resources it created') and explicitly covers the second mode (list releases in the org). The two-mode framing separates it cleanly from siblings like install_template, upgrade_template, browse_templates, and uninstall_template.

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?

Gives concrete usage conditions: omit `name` to list, supply `name` plus waitSeconds to block until deployed and workloads are ready, and 'use this instead of calling again and again' to steer away from polling. It stops short of naming a specific sibling (e.g., browse_templates for discovering installable templates), so it is clear but not fully disambiguating.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Control Plane tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.