Skip to main content
Glama

hf_space_restart

Restart or wake a Hugging Face Space by ID to resume its runtime; note that billing resumes if it runs on paid hardware.

Instructions

Restart (or wake) a Space. On paid hardware, billing resumes.

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": {
      "space_id": "<space_id>"
    },
    "name": "hf_space_restart"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral information itself. It does usefully disclose that billing resumes on paid hardware, which is a non-obvious cost consequence; however, it says nothing about authentication requirements, whether existing state or configuration is preserved across the restart, or what failures look like.

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?

Two short sentences, front-loaded with the action and followed by the billing consequence. Nothing is wasted, though the parenthetical "(or wake)" could be folded into a cleaner single statement.

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: one required parameter and an output schema, so return values need no explanation. Still, an agent lacks guidance on the pause/restart pairing and on the space_id format, both of which the description could have supplied cheaply.

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% for the single space_id parameter, but the parameter name is self-explanatory and the description does not contradict it. The description adds no detail about the identifier's format (e.g. "owner/space-name"), leaving the only gap unaddressed.

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?

"Restart (or wake) a Space" gives a specific verb and resource, and the parenthetical clarifies that a stopped Space can also be woken. It does not distinguish itself from hf_space_pause, the obvious opposite operation, even though that sibling exists.

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 phrase "or wake" implies the context in which this tool is useful (a paused or sleeping Space), but there is no explicit statement of when to use it rather than hf_space_pause or hf_space_status, and no prerequisites are mentioned.

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