Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Hugging Face Spaces by meaning

hugging_face_spaces_semantic_search
Read-onlyIdempotent

Search Hugging Face Spaces that match a plain-words description to find relevant demos, with optional SDK or category filters.

Instructions

Search Hugging Face Spaces that match a plain-words description. Requires query. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
sdkNoOnly Spaces built with this SDK.
queryYesRequired. What you are looking for, in plain words.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
categoryNoOnly Spaces in this category.
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

C2.9/5.0
Behavior2/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 fully covered. The description adds only "Returns a list," saying nothing about result size, ranking, pagination, or the stateful conversation_id handshake that governs whether calls can be parallelized.

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?

Three short, front-loaded sentences with no padding, and the core purpose leads. The middle sentence ("Requires `query`") is redundant with the schema's required list and could be dropped.

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?

With 6 parameters, 3 required, and no output schema, the description is just barely sufficient: the schema does the heavy lifting on parameters and annotations cover safety. It omits the notable statefulness implied by conversation_id and says almost nothing about what the returned list contains.

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 query, context, llm_model, sdk and category are all documented in the schema itself. The description restates only that query is required, adding no meaning beyond the schema; baseline 3 applies.

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 (search Hugging Face Spaces) and adds a semantic qualifier ("match a plain-words description"), which distinguishes it in spirit from the keyword sibling hugging_face_spaces_search. It never names that sibling explicitly, so the differentiation is implicit rather than guaranteed.

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?

The only usage signal is the phrase "plain-words description," which hints at natural-language queries. There is no statement of when to prefer this over hugging_face_spaces_search, no prerequisites, and no exclusions.

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