Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hugging Face paper full text

hugging_face_papers_content_get
Read-onlyIdempotent

Retrieves the full text of a Hugging Face paper as Markdown from its arXiv ID, so you can read or process the complete paper content.

Instructions

Get the full text of a Hugging Face paper as Markdown. Requires arxivId.

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

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the return format (Markdown), which is genuinely useful for planning downstream parsing. It says nothing about response size, truncation, or failure behavior for an unknown arXiv id.

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, front-loaded sentences with the format stated first. The second sentence largely duplicates the schema's required-field list, so it earns only marginal space, but nothing is verbose.

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?

For a simple read-only fetch with full schema coverage and no output schema, the definition covers purpose, return format, and the key required input. Missing only edge-case behavior (invalid/unknown arXiv id, long-paper handling), which is a minor 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 coverage is 100% and the arxivId pattern/version-suffix behavior is fully documented in the schema itself. The description's 'Requires `arxivId`' merely restates the required list and adds no meaning beyond the schema, so the 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?

States a specific verb and resource ('Get the full text of a Hugging Face paper') plus the return format (Markdown), which is more informative than the title alone. It does not distinguish itself from the likely metadata sibling hugging_face_papers_get, so an agent must infer the boundary between full text and paper metadata.

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 cue is the prerequisite 'Requires `arxivId`'. There is no statement of when to prefer this over hugging_face_papers_get or hugging_face_papers_search, and no note about cost/size of fetching full text versus metadata.

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