Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hugging Face Space

hugging_face_spaces_get
Read-onlyIdempotent

Retrieve a Hugging Face Space's run state, hardware, SDK, and linked models and datasets by owner and name to inspect how a Space is configured and running.

Instructions

Get a Hugging Face Space with its run state, hardware, SDK and linked models and datasets. Requires owner and name.

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": {
      "owner": "<owner>",
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_spaces_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Repository name, without the owner.
ownerYesRequired. Owner of the repository: a user or organization name.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
revisionNoBranch, tag or commit. Default: the default branch (`main`).
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful return-content context (run state, hardware, SDK, linked models/datasets), which matters since there is no output schema, but it omits access behavior for private/gated Spaces and any error/not-found semantics.

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 front-loaded sentences with the returned fields stated first and no padding. The trailing "Requires `owner` and `name`" is largely redundant with the schema's required list, costing a bit of space.

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, the description usefully previews what comes back, which is the main completeness burden here. Gaps remain around private-repo access and revision effects, but for a straightforward single-repository read the coverage is adequate.

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 100%, so the schema already documents owner, name, revision and the harness parameters; baseline 3 applies. The description adds no meaning beyond the schema—it only repeats that owner and name are required and says nothing about how revision changes the result.

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 states a specific verb and resource ("Get a Hugging Face Space") and enumerates the payload (run state, hardware, SDK, linked models and datasets). It does not name a sibling such as hugging_face_spaces_search to distinguish a direct fetch-by-identifier from a search, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to call this only when owner and name are already known, or to prefer hugging_face_spaces_search / semantic_search when they are not. "Requires `owner` and `name`" restates the schema's required fields rather than routing the agent among alternatives.

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

Deploy Server

Other Tools