Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face paper repositories

hugging_face_papers_repos_list
Read-onlyIdempotent

List Hugging Face models, datasets, and Spaces that cite a given arXiv paper. Provide the arXiv ID to see which projects reference it.

Instructions

List the Hugging Face models, datasets and Spaces that cite a paper. Requires arxivId. 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": {
      "arxivId": "<arxivId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_papers_repos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
arxivIdYesRequired. arXiv id of the paper, e.g. `1706.03762`. A version suffix (`v2`) is ignored: Hugging Face keeps one page per paper.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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, non-destructive and openWorld, so safety is covered. The description adds only 'Returns a list' — no information on result size, pagination, ordering, or whether repositories are grouped by type, which are the behaviors an agent would still want to know.

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 sentences with the outcome stated first and no filler; the only slight waste is restating the required parameter, which the schema already enforces.

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?

This is a simple read-only list tool with fully described parameters and no output schema, so the description is close to sufficient. However, with no output schema the agent gets no sense of the returned item shape or list size, leaving a modest gap.

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%, including an explicit pattern and a note that version suffixes are ignored, so the schema carries parameter meaning. The description merely repeats that arxivId is required and adds nothing new about the parameter's semantics.

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: list models, datasets and Spaces that cite a given paper. That scope is unambiguous and distinct from paper-fetching siblings like hugging_face_papers_get or papers_search, though it does not explicitly name those alternatives.

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?

Only a prerequisite is given ('Requires `arxivId`'), which is already enforced by the schema's required array. There is no guidance on when to pick this over another papers tool or on any preconditions beyond the id.

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