Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hugging Face readme

hugging_face_repos_readme_get
Read-onlyIdempotent

Fetches the README of a Hugging Face model, dataset or Space by owner and name, so you can inspect repository setup, usage and requirements without leaving your editor.

Instructions

Get the README of a Hugging Face model, dataset or Space. Requires repoType, 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": {
      "repoType": "<repoType>",
      "owner": "<owner>",
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_repos_readme_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.
repoTypeYesRequired. Repository type: `models`, `datasets` or `spaces`.
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
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 covered. The description adds nothing beyond that — it does not say what happens when a repository has no README, whether the revision parameter affects the fetched content, or how the README body is returned.

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 sentences with the resource and scope front-loaded and no filler. The second sentence is largely redundant with the schema's required-field metadata, which keeps it from a 5.

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 fetch with fully documented parameters and safe-by-default annotations, so most of what an agent needs is present. However, with no output schema, the description should indicate that the return value is the README text itself (and how absence is signalled), which it omits.

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% and every parameter, including revision, context and llm_model, is documented in the schema. The description only restates the three required identifying parameters and adds no syntax or behavioral nuance beyond the schema, so the baseline of 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 ('Get the README') and names the three applicable entity types (model, dataset, Space), which is meaningfully more precise than the tool name alone. It does not explicitly distinguish itself from the file-listing sibling or explain what form the README is returned in, so a 4 rather than 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 Guidelines3/5

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

The usage context is implied by the repo-type enumeration, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to alternatives such as the files-listing tool for raw file access. The agent must infer that this is for documentation content specifically.

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