Skip to main content
Glama

hf_runtime_connect

Attach to an existing Hugging Face runtime, report progress while it starts, and reconnect to the same kernel once ready.

Instructions

Attach to the Hugging Face runtime started with hf_runtime_start.

Safe to call repeatedly and in every new session: it reports progress while the machine is still starting, and re-attaches to the same kernel once it is up.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hf_runtime_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral load and does well: it discloses idempotency/repeat safety, progress reporting during machine startup, and re-attachment to the same kernel once running. Gaps remain around failure modes and authentication expectations, but the core behavioral traits are unusually clear.

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 operation and lifecycle precondition, with every clause adding useful information about idempotency and startup behavior. No wasteful wording.

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?

The tool is simple and has an output schema, and the description covers its core attach behavior, precondition, and repeat-call safety. However, for an agent that needs to decide how long to wait or how to interpret wait_seconds, the omission is a real completeness gap.

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 the single wait_seconds parameter, and the description never mentions it or explains whether it is a maximum blocking duration, poll interval, or startup timeout. The parameter name and default are suggestive, but meaningful semantics are missing.

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?

The description uses a specific verb ("Attach to") and a precise resource ("the Hugging Face runtime started with hf_runtime_start"), which distinguishes it from the start sibling by making the runtime lifecycle position explicit. An agent can identify the operation 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 Guidelines4/5

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

It clearly states the prerequisite (a runtime started with hf_runtime_start) and that repeated calls in every new session are safe, which tells the agent when to use it. It does not explicitly route to alternatives such as runtime_status or connect_runtime, but the lifecycle condition is strong guidance.

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