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). 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	Default
`org`	Yes	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.
`name`	Yes	Release name — the unique, immutable identifier for this installed instance within the org.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the call succeeded.
`data`	No	The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary.
`summary`	Yes	One-line summary of the result.
`nextSteps`	No	Recommended follow-up actions for this task, in order.

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, non-destructive), the description discloses a significant behavioral requirement: the token must have `reveal` permission on the helm bookkeeping secret. It also states that values and manifests are never included, adding context that the annotations do not cover. No contradiction with 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?

Three sentences, each earning its place: first states the functionality, second states an exclusion, third states a permission requirement. The description is front-loaded with the verb 'Show' and contains no redundant information.

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 is present, so the description does not need to explain return values. It covers purpose, scope, exclusions, and permission requirements, which is sufficient for a 2-parameter read-only tool. The description is complete for an agent to decide whether to invoke it.

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?

The input schema has 100% description coverage for both parameters, with detailed explanations (org pattern and release name immutability). The description adds no parameter-specific guidance beyond the overall action. According to the rubric, baseline 3 applies when schema coverage is high and the description does not add extra param semantics.

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 uses the specific verb 'Show' with a clear resource ('an installed release') and enumerates the returned data (status, revision, resources with kind, name, link). It also explicitly states what is excluded ('install values and manifests are never included'), which distinguishes it from sibling tools like get_template or 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 Guidelines5/5

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

The description provides an explicit when-to-use: when needing an installed release's current status, revision, and created resources. It also gives a clear when-not-to-use by stating that install values and manifests are never included, signaling that the tool is not appropriate for those needs. This is an explicit exclusion criterion, though it does not name an alternative tool.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Every tool targets a distinct resource/action pair (e.g., get_resource vs get_resource_schema, list_deployments vs list_workload_replicas) and descriptions clearly differentiate purposes. No two tools appear to do the same thing.

Naming Consistency5/5

All tools follow a verb_noun snake_case pattern (create_gvc, update_workload, list_resources, query_metrics) with consistent verbs. The few imperative verbs (browse, build, mount) still maintain the same verb-first structure.

Tool Count1/5

With 55 tools, this server far exceeds the typical well-scoped 3-15 tool range. While each tool appears purposeful, the sheer number creates selection overhead and falls into the extreme 50+ category on the rubric.

Completeness4/5

The surface covers nearly the full Control Plane lifecycle: CRUD for GVC, workload, identity, policy, volumeset, and domain, plus observability, templates, image builds, and Terraform. Minor gaps include referenced but missing configure_workload_* tools and no secret creation/deletion (by design).