Skip to main content
Glama

Claim a consumer runner pairing

claim_runner_pairing
Destructive

Claims a short-lived pairing ID and binds it to one SignalR block for integration testing or manual pairing, enabling secure runner device setup.

Instructions

Claims a short-lived pairingId created by a generic consumer runner and binds it to one SignalR block. Use this for integration testing or an explicitly requested manual pairing. In production the application's authenticated BACKEND must call the same Management API route after mapping its own user to the device; never put the Management credential in browser code. The pairingId expires and is single-claim.

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>",
      "pairingId": "<pairingId>"
    },
    "name": "claim_runner_pairing"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoUser-facing computer name.
confirmNoMust be true because this creates a durable runner device.
pairingIdYesOpaque pairing id received by the application's HTTPS handoff page.
signalRBlockIdYesThe SignalR block guid (signalRGuid).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true; the description adds the substantive context the annotations cannot: the pairingId is short-lived and single-claim, the operation creates a durable runner device, and the credential must stay server-side. This is exactly the behavioral value-add expected beyond structured hints.

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?

Three sentences, each earning its place: what it does, when to use it, and the security/production caveat. The most consequential information (credential placement, expiry, single-claim) is packed into tight phrasing with no filler.

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

Completeness5/5

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

For a 4-parameter mutation with no output schema, the description covers purpose, correct usage context, and critical constraints (expiry, single claim, server-side credential). Nothing an agent needs in order to call this correctly appears to be missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning to pairingId ('created by a generic consumer runner', short-lived, single-claim) and to the destination ('binds it to one SignalR block'). It still does not clarify the `name` or `confirm` parameters beyond the schema text.

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 and resource ('claims a short-lived pairingId ... binds it to one SignalR block') and distinguishes itself from the production path where the authenticated backend calls the same route. An agent can tell exactly what this does without opening the schema.

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 names when to use it ('integration testing or an explicitly requested manual pairing') and when not to ('In production the application's authenticated BACKEND must call the same Management API route'). It even warns against the wrong environment ('never put the Management credential in browser code').

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