Control Plane

Get Installed Template Resources

get_installed_template

Read-onlyIdempotent

Show an installed release’s current status, revision, and the Control Plane resources it created (kind, name, link). Pass waitSeconds 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. Requires the token to have reveal permission on the release’s helm bookkeeping secret, where release state is stored.

Input Schema

TableJSON Schema

Name	Required	Description
`org`	No	Organization slug.
`name`	Yes	Release name — the unique, immutable identifier for this installed instance within 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

TableJSON 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.

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.5/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description still adds substantive context beyond them: what is explicitly excluded from the response (install values and manifests), the required `reveal` permission on the release's helm bookkeeping secret, and the timeout behavior of waitSeconds. This is genuinely information the agent could not derive from the annotations.

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

Conciseness5/5

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

Four sentences, each carrying distinct load: purpose and return shape first, then the wait option, then response boundaries, then the auth requirement. No filler or hedging, and the most important content is front-loaded.

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?

An output schema exists, so return values need not be enumerated, yet the description still supplies the security-relevant boundaries (metadata only) and the prerequisite permission. For a read-only, single-resource status lookup with one optional behavior flag, nothing material is 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 description coverage is 100%, so org, name, and waitSeconds are already fully documented, including the 0–45 range and timeout semantics; the description mostly restates waitSeconds' purpose and adds no format or syntax detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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 verb (show) and resource (an installed release) plus exactly what is returned: status, revision, and the Control Plane resources created with their kind/name/link. The 'installed release' framing and the note that it returns release metadata only cleanly separate it from get_template, browse_templates, and list_installed_templates.

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 clear operational context: use waitSeconds to block until the release is deployed and every workload is ready, explicitly framed as a substitute for repeated polling ('Use this instead of calling again and again'). It does not name sibling tools or state exclusions (e.g., when to prefer list_installed_templates or get_resource instead), so it stops short of full routing guidance.

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.