Skip to main content
Glama
runwhen-contrib

RunWhen Platform MCP

deploy_registry_codebundle

Deploy a pre-built registry codebundle to a workspace as an SLX. Uses repo URL, codebundle path, and other registry values for configuration.

Instructions

Deploy a registry codebundle as an SLX to a workspace.

Unlike commit_slx (which embeds inline scripts via the Tool Builder codebundle), this deploys a pre-built codebundle from its own codecollection repository. The runbook.robot / sli.robot live in the codebundle's git repo — no inline script is needed.

Use search_registry + get_registry_codebundle to find the right codebundle, then call this tool with the values from the registry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoGit branch/tag for the codecollection.main
dataNo'logs-bulk', 'config', or 'logs-stacktrace'.logs-bulk
tagsNoResource tags ({name, value} dicts).
aliasYesHuman-readable display name (e.g. 'Namespace Health').
accessNo'read-only' or 'read-write'.read-only
branchNoWorkspace config branch.main
ownersNoOwner emails (defaults to current user).
locationYesRunner location (use get_workspace_locations).
repo_urlYesGit URL of the codecollection.
slx_nameYesShort SLX name (lowercase-kebab-case).
hierarchyNoTag names for hierarchical grouping.
image_urlNoIcon URL for the SLX.
statementYesSLX statement (e.g. 'All pods should be running').
deploy_sliNoAlso deploy the SLI (health indicator).
config_varsNoCodebundle config variables.
secret_varsNoSecret mappings (e.g. {'kubeconfig': 'kubeconfig'}).
resource_pathNoResource path for search indexing.
commit_messageNoCustom commit message.
deploy_runbookNoDeploy the runbook (task).
workspace_nameYesTarget workspace (e.g. 't-oncall').
codebundle_pathYesPath to codebundle dir (e.g. 'codebundles/k8s-namespace-healthcheck').
sli_descriptionNoDescription for the SLI metric.
sli_interval_secondsNoSLI run interval in seconds.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It explains that the tool deploys a pre-built codebundle from its own repo and mentions the runbook/sli location. While it doesn't detail auth or side effects, the overall behavior is clear. A 4 is appropriate as it adds useful context beyond the basic operation.

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?

The description is concise (5 sentences), front-loaded with the main purpose, and well-structured. It includes a sibling comparison and usage instructions with no wasted words.

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?

Given the complexity (23 params, 7 required, output schema exists), the description provides essential context: purpose, sibling differentiation, and preparation steps. There is an output schema, so return values need not be described. A 4 reflects that it covers the key aspects without being overly detailed.

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 all 23 parameters. The description does not add extra meaning beyond referencing 'values from the registry'. The baseline 3 is correct since the description doesn't enhance parameter understanding.

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 clearly states the tool deploys a registry codebundle as an SLX to a workspace, with specific verb and resource. It distinguishes itself from the sibling commit_slx by contrasting the deployment of pre-built codebundles versus inline scripts.

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 explicit guidance on when to use this tool: after using search_registry and get_registry_codebundle to find the right codebundle. It also contrasts with commit_slx, helping the agent choose the correct tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/runwhen-contrib/runwhen-platform-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server