Skip to main content
Glama

Check what the app's users are running

get_runner_release_status
Read-only

Check a runner block's release status: published release, in-flight build, last failure, and drift since release, including author compiler errors for failed builds.

Instructions

Reports the published release, any build in flight, the last failure and whether the block's handler has been edited since it was released (drift). A failed build reports the author's own compiler error. drift: null means nothing has ever been released, which is not the same as being up to date.

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_runner_release_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
signalRBlockIdYes
runtimeIdentifierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations only mark it read-only, so credit goes to the description for disclosing what is actually returned: the published release, an in-flight build, the last failure including the author's own compiler error, and drift since release. The clarification that `drift: null` means nothing was ever released (not 'up to date') is a genuinely useful semantic distinction that annotations would never convey.

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 short sentences, front-loaded with the reported facts and ending on the interpretive caveat about null drift. Nothing is redundant, though the parenthetical `drift` gloss is slightly compressed and could be cleaner.

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?

With no output schema, the description does a decent job naming the returned fields, which is the main burden. However, it leaves both input parameters completely unexplained, so an agent still has to open the schema and guess at `runtimeIdentifier`'s role before calling.

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% for two parameters, yet the description never mentions `signalRBlockId` (the required argument) or `runtimeIdentifier` (the enum-constrained optional). The reader gets no hint about what block ID means here or when to supply a runtime identifier, so the description fails to compensate for the schema gap.

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 description uses a specific verb (reports) and enumerates the exact facts returned: published release, in-flight build, last failure, and handler drift. That is far more informative than the name alone. It stops short of naming a sibling such as get_runner_artifact_status to draw the boundary, so a 4 rather than a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no reference to an alternative tool. The reader can infer this is a lookup for release state, but nothing tells them whether to prefer get_runner_artifact_status or get_consumer_runner_download in a given situation.

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