Skip to main content
Glama

hf_space_pause

Pause a Hugging Face Space to stop its runtime and billing until you restart it. Use this when you need to halt GPU usage without deleting the Space.

Instructions

Pause a Space: it stops running and stops billing until restarted.

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

Input Schema

NameRequiredDescriptionDefault
space_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral facts: the Space stops running, billing stops, and the state is reversible by restarting. It omits what happens to in-flight requests, jobs, or stored state during a pause, and does not mention permissions or whether the pause is immediate.

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?

A single front-loaded sentence with the action first and the consequence second; every clause earns its place and there is no redundant restatement of the name.

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?

An output schema exists, so return values need not be described, and reversibility is covered. Still missing for a mutation-style lifecycle tool with no annotations: identifier format, permission requirements, and any side effects on running work, which leaves the definition only minimally sufficient.

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?

There is one required parameter, space_id, and schema description coverage is 0%, so neither the schema nor the description explains its expected form (owner/name slug vs. numeric id). The description adds no parameter information at all, leaving the agent to guess the identifier format.

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 gives a specific verb and resource ("Pause a Space") and states the operational effect, so an agent can tell it apart from restart or status tools in the sibling list. It does not explicitly name those siblings, so differentiation is inferred rather than stated.

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 "until restarted" implies the resume path and that halting billing is the motivation for using this tool, which is useful implied guidance. However, it never says when not to use it or points to hf_space_restart or hf_runtime_stop as the follow-up, so an agent must infer the workflow.

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