Control Plane

Get a Control Plane Skill

get_cpln_skill

Read-onlyIdempotent

Returns the runbook for one Control Plane task family: how to use the feature correctly, the platform constraints that are easy to miss, and when it is the wrong tool. Optional deep reference for work the job tools (deploy_app, add_database, and the rest) do not cover. Rules that apply to every task (approvals, Terraform ownership, failures) are in the operating-guide skill. Pass section to read one part.

Input Schema

Name	Required	Description	Default
`skill`	Yes	Skill to read.
`section`	No	Read only this section, by heading. A full read starts with the list of section headings.

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.

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / skill / enum

Previous value: -[
-  "access-control",
-  "audit-compliance",
-  "autoscaling-capacity",
-  "cdn-rate-limiting",
-  "cpln",
-  "create-app",
-  "domain",
-  "environment-promotion",
-  "external-logging",
-  "firewall-networking",
-  "gitops-cicd",
-  "iac-terraform-pulumi",
-  "image",
-  "ipset-load-balancing",
-  "k8s-operator",
-  "logql-observability",
-  "metrics-observability",
-  "migration-patterns",
-  "mk8s-byok",
-  "native-networking",
-  "org-management",
-  "query-spec",
-  "setup-agent",
-  "setup-cloud-access",
-  "setup-secret",
-  "stateful-storage",
-  "tag",
-  "template-catalog",
-  "workload",
-  "workload-security",
-  "workload-troubleshooting"
-]New value: +[
+  "access-control",
+  "audit-compliance",
+  "autoscaling-capacity",
+  "cdn-rate-limiting",
+  "cpln",
+  "create-app",
+  "domain",
+  "environment-promotion",
+  "external-logging",
+  "firewall-networking",
+  "gitops-cicd",
+  "iac-terraform-pulumi",
+  "image",
+  "ipset-load-balancing",
+  "k8s-operator",
+  "logql-observability",
+  "metrics-observability",
+  "migration-patterns",
+  "mk8s-byok",
+  "native-networking",
+  "org-management",
+  "query-spec",
+  "setup-agent",
+  "setup-cloud-access",
+  "setup-secret",
+  "stateful-storage",
+  "tag",
+  "template-catalog",
+  "workload",
+  "workload-security",
+  "workload-troubleshooting",
+  "operating-guide"
+]

Changed11 schema fields changedSep 30, 2026

removedInput schema / $schema

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

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

addedInput schema / properties / section

Added value: +{
+  "description": "Read only this section, by heading. A full read starts with the list of section headings.",
+  "type": "string"
+}

changedInput schema / properties / skill / description

Previous value: -"Skill to read — tools name their skill as \"recommended reading\". Available: access-control, audit-compliance, autoscaling-capacity, cdn-rate-limiting, cpln, create-app, domain, environment-promotion, external-logging, firewall-networking, gitops-cicd, iac-terraform-pulumi, image, ipset-load-balancing, k8s-operator, logql-observability, metrics-observability, migration-patterns, mk8s-byok, native-networking, org-management, query-spec, setup-agent, setup-cloud-access, setup-secret, stateful-storage, tag, template-catalog, workload, workload-security, workload-troubleshooting."New value: +"Skill to read."

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."
```

Changed2 schema fields changedSep 22, 2026

changedInput schema / properties / skill / description

Previous value: -"Skill to read — tools name their skill as \"recommended reading\". Available: access-control, audit-compliance, autoscaling-capacity, cdn-rate-limiting, cpln, domain, environment-promotion, external-logging, firewall-networking, gitops-cicd, iac-terraform-pulumi, image, ipset-load-balancing, k8s-operator, logql-observability, metrics-observability, migration-patterns, mk8s-byok, native-networking, org-management, query-spec, setup-agent, setup-cloud-access, setup-secret, stateful-storage, tag, template-catalog, workload, workload-security, workload-troubleshooting."New value: +"Skill to read — tools name their skill as \"recommended reading\". Available: access-control, audit-compliance, autoscaling-capacity, cdn-rate-limiting, cpln, create-app, domain, environment-promotion, external-logging, firewall-networking, gitops-cicd, iac-terraform-pulumi, image, ipset-load-balancing, k8s-operator, logql-observability, metrics-observability, migration-patterns, mk8s-byok, native-networking, org-management, query-spec, setup-agent, setup-cloud-access, setup-secret, stateful-storage, tag, template-catalog, workload, workload-security, workload-troubleshooting."

changedInput schema / properties / skill / enum

Previous value: -[
-  "access-control",
-  "audit-compliance",
-  "autoscaling-capacity",
-  "cdn-rate-limiting",
-  "cpln",
-  "domain",
-  "environment-promotion",
-  "external-logging",
-  "firewall-networking",
-  "gitops-cicd",
-  "iac-terraform-pulumi",
-  "image",
-  "ipset-load-balancing",
-  "k8s-operator",
-  "logql-observability",
-  "metrics-observability",
-  "migration-patterns",
-  "mk8s-byok",
-  "native-networking",
-  "org-management",
-  "query-spec",
-  "setup-agent",
-  "setup-cloud-access",
-  "setup-secret",
-  "stateful-storage",
-  "tag",
-  "template-catalog",
-  "workload",
-  "workload-security",
-  "workload-troubleshooting"
-]New value: +[
+  "access-control",
+  "audit-compliance",
+  "autoscaling-capacity",
+  "cdn-rate-limiting",
+  "cpln",
+  "create-app",
+  "domain",
+  "environment-promotion",
+  "external-logging",
+  "firewall-networking",
+  "gitops-cicd",
+  "iac-terraform-pulumi",
+  "image",
+  "ipset-load-balancing",
+  "k8s-operator",
+  "logql-observability",
+  "metrics-observability",
+  "migration-patterns",
+  "mk8s-byok",
+  "native-networking",
+  "org-management",
+  "query-spec",
+  "setup-agent",
+  "setup-cloud-access",
+  "setup-secret",
+  "stateful-storage",
+  "tag",
+  "template-catalog",
+  "workload",
+  "workload-security",
+  "workload-troubleshooting"
+]

First observedJun 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered; the description adds the non-obvious behavioral detail that a full read begins with a list of section headings, which tells the agent how to discover sections before drilling in. It does not mention size/length or cost of a full read, which is the one behavioral trait an agent would still want.

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?

Four sentences, each carrying distinct information, with the core verb-and-resource statement front-loaded. The parenthetical '(deploy_app, add_database, and the rest)' is slightly loose but reinforces the routing quickly; nothing is redundant.

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?

For a two-parameter read tool with an output schema, full annotations, and a 100%-described schema, the description covers what it returns, when to prefer it, when to prefer the operating-guide instead, and how to navigate sections. Nothing an agent needs to call it 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% and the enum is self-documenting, so the baseline is 3. The description earns above that by explaining what 'skill' means semantically (one Control Plane task family) and how section interacts with a full read ('Pass section to read one part'; a full read starts with headings), which is workflow guidance the schema does not give.

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 and resource ('Returns the runbook for one Control Plane task family') and enumerates the content: correct usage, easy-to-miss platform constraints, and when the feature is the wrong tool. It explicitly separates itself from the job tools (deploy_app, add_database) and from the operating-guide skill, so an agent can place it against siblings 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 both a use case ('optional deep reference for work the job tools do not cover') and an explicit routing rule away from this tool ('Rules that apply to every task ... are in the operating-guide skill'). The word 'optional' also sets the priority relative to the action tools, which is exactly the disambiguation an agent needs.

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.