Skip to main content
Glama

Get the public Consumer App Runner download

get_consumer_runner_download
Read-only

Returns the direct HTTPS .exe download URL to embed in a consumer app UI. The file holds no credentials; identity is created only after the app authenticates the user.

Instructions

Returns the direct HTTPS .exe URL an application must show to its end users. The executable contains no credential: downloading creates no device, and identity is created only after the application authenticates the user and claims pairing. When building a consumer application, put this URL in its UI and verify the artifact is available before calling the app complete. If the reply carries unsignedWarning, that warning belongs on the page beside the link.

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": "get_consumer_runner_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
signalRBlockIdYes
runtimeIdentifierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses meaningful behavior: the executable contains no credential, downloading creates no device, and identity exists only after authentication and pairing claim. It also pre-empts an output field the schema does not declare, instructing that any unsignedWarning in the reply must be surfaced beside the link.

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?

The return value is front-loaded in the first sentence, and the remaining sentences each carry distinct operational content without repetition. It runs four sentences but none is padding; the pairing explanation is the least essential yet still grounds why no device appears.

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 no output schema, the description does the job of explaining the return (a URL plus a possible unsignedWarning) and its downstream obligation. The main hole is the undocumented required signalRBlockId and the absence of any failure or unavailability behavior, which matters for a fetch-an-artifact tool.

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%, so the description must carry parameter meaning, and it does not. signalRBlockId is never mentioned or explained, and runtimeIdentifier is left entirely to its enum values (win-x64/win-arm64) with no note on what choice implies.

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?

The first sentence names a specific verb and resource: it returns a direct HTTPS .exe URL for a consumer App Runner, and it clarifies the audience (end users of a consumer application). The purpose is unambiguous, but it never contrasts itself with related operations like get_runner_artifact_status or setup_runner, so sibling differentiation is left to the reader.

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

Usage Guidelines4/5

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

It gives a clear usage context: 'When building a consumer application, put this URL in its UI and verify the artifact is available before calling the app complete.' That tells the agent where the value belongs in a workflow. It stops short of naming alternatives or stating when-not to use it, so the guidance is contextual rather than routing.

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