Skip to main content
Glama

Release this handler to the app's users

release_runner_handler

Compiles a block's current handler into a downloadable executable and publishes it as the installer, creating the consumer download link. Requires confirm:true; poll release status until published.

Instructions

Compiles the block's CURRENT handler into the executable its end users download, and makes that the published installer. This is what gives a consumer application a working download link: without a release there is no artifact and no link. The build runs out of process and takes a few minutes — poll get_runner_release_status, or get_consumer_runner_download, until it reports published. Requires confirm:true: it distributes an executable to other people.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "signalRBlockId": "<signalRBlockId>"
    },
    "name": "release_runner_handler"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
signalRBlockIdYes
runtimeIdentifierNo
consumerPairingUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the lone destructiveHint:false annotation by disclosing that the build runs out of process, takes a few minutes, is asynchronous, requires confirm:true, and distributes an executable to other people. It does not say what happens on a repeat release to an already-published handler, or whether the prior installer is replaced, which is the remaining meaningful gap.

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 sentences, front-loaded with the core action, with the preconditions and polling guidance following in priority order. The 'without a release there is no artifact and no link' clause restates the preceding sentence somewhat, costing a little density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the async lifecycle and confirmation gate well for a no-output-schema mutation tool, but with zero schema coverage and no output schema it leaves half the parameter surface unexplained. An agent learns how to wait but not what runtimeIdentifier or consumerPairingUrl change about the produced artifact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 4 parameters, and the description only explains one of them meaningfully (confirm:true, justified by distributing an executable). runtimeIdentifier (enum win-x64/win-arm64) and consumerPairingUrl are never mentioned, and signalRBlockId is only obliquely implied by "the block's CURRENT handler".

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 chain and resource: compiles the block's CURRENT handler into the executable end users download and makes it the published installer. It also explains the outcome (a working download link) which distinguishes it from get_runner_release_status and get_consumer_runner_download, which merely report state.

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?

Explicitly frames when this tool is needed (no release means no artifact and no link) and routes the agent to the correct alternatives for waiting: poll get_runner_release_status or get_consumer_runner_download until published. It also states the confirm:true precondition, so no ambiguity about invocation.

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