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 do not cover. Pass section to read one part.

Input Schema

TableJSON 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

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.

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds useful framing about what the returned runbook contains, but with an output schema present there is little extra behavioral disclosure needed, and none is provided beyond the content summary.

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 tight sentences, front-loaded with the return value and followed by the content scope and the section hint. No filler or repetition, though the final sentence borders on redundant with the schema.

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?

With an output schema, full annotation coverage, and 100% parameter description coverage, the description only needs to convey intent and scope, which it does. The main gap is routing guidance relative to the many sibling reference tools.

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 the schema already documents both 'skill' and 'section'. The description's 'Pass section to read one part' merely restates the schema's section semantics without adding syntax, defaults, or interaction detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 types (usage guidance, platform constraints, when it's the wrong tool). It does not, however, distinguish itself from the similarly named sibling get_cpln_rules or explain the relationship to the 'job tools' it references.

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

Usage Guidelines3/5

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

'Optional deep reference for work the job tools do not cover' gives an implicit usage condition, but 'job tools' is never named and no sibling (e.g., get_cpln_rules, search_control_plane) is cited as an alternative. The reader must infer when to reach for this versus other reference/lookup tools.

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.