Skip to main content
Glama

Check consumer runner artifact

get_runner_artifact_status
Read-only

Check whether an immutable consumer runner is published for a SignalR block and platform, returning its version and signature level without building or downloading.

Instructions

Checks whether an immutable consumer runner is published for a SignalR block and platform, including its version and signature level. This does not build, publish, or download anything.

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

Input Schema

NameRequiredDescriptionDefault
signalRBlockIdYes
runtimeIdentifierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so credit goes to what the description adds: it discloses what information comes back (version and signature level) and explicitly disclaims side effects like building or publishing. It does not say what happens when nothing is published (error vs. negative result), which is the one behavioral gap.

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?

Two sentences, front-loaded with the core action and followed by a single high-value exclusion. No filler, no restatement of the title.

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 and zero parameter documentation, the description does the necessary work by naming the returned fields and the read-only nature. It falls short only on the not-published case and on runtimeIdentifier optionality, both of which matter for correct invocation.

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 0%, so the description must carry meaning, and it partially does by mapping the call to a SignalR block plus a platform, which correspond to signalRBlockId and runtimeIdentifier. It never clarifies that runtimeIdentifier is optional or what omitting it means, leaving a real gap at 0% schema coverage.

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: checks whether an immutable consumer runner is published for a SignalR block and platform, and names what is reported (version, signature level). It does not explicitly contrast with close siblings such as get_runner_release_status or get_consumer_runner_download, so sibling differentiation is left implicit.

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?

The closing sentence 'This does not build, publish, or download anything' usefully rules out the download path and marks this as a pure lookup. However, it never says when to prefer this over get_runner_release_status, nor what prerequisite state (e.g. block published, platform chosen) makes the call meaningful.

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