Skip to main content
Glama

NS Pros MCP Gateway

huggingface__hf_fs

When to use: Hugging Face Hub models, datasets, Spaces, collections, papers, daily papers, today's trending models, current paper leaderboard, docs; list and read repository files, model and dataset cards (README, license).

Examples: {"operations":[{"cmd":"ls","args":["hf://models/trending","--limit","10"]}]} {"operations":[{"cmd":"ls","args":["hf://papers/trending"]}]} {"operations":[{"cmd":"ls","args":["hf://papers/daily/latest"]}]} {"operations":[{"cmd":"cat","args":["hf://papers/250

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": {
      "operations": "<operations>"
    },
    "name": "huggingface__hf_fs"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly does not meet it. It never states that the tool is read-only (no write command exists in the enum), says nothing about authentication/token requirements, rate limits, pagination semantics beyond a bare '--limit' in an example, or what a listing entry looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The 'When to use' line is front-loaded and dense with useful resource scopes, and the examples are the right format for a command-dispatch tool. The text is cut off mid-example ('hf://papers/250'), leaving an incomplete and slightly confusing body.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the definition should explain return shape, errors and per-command behavior, and it does none of these. For a dispatch tool with a six-value command enum, the description covers only the listing case and leaves an agent guessing about cat/find/search/attach.

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?

Reported schema coverage is 0%, so the description must compensate, and it does partially: the JSON examples reveal that the top-level 'operations' array holds objects with 'cmd' and 'args', and show the hf:// URI convention. However only two of the six enum commands (ls, cat) are illustrated, and attach/stat/find/search semantics are left entirely to the schema.

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 names concrete resources and verbs: 'list and read repository files, model and dataset cards (README, license)' across models, datasets, Spaces, collections and papers. An agent can tell this is a virtual-filesystem reader over hf:// URIs. It never explicitly distinguishes itself from hub_repo_search or hub_repo_details, so sibling differentiation is left implicit.

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 'When to use' preamble gives positive context (models, datasets, Spaces, collections, papers, trending, leaderboard, docs), which is real guidance. There are no when-not-to-use statements, no routing to sibling tools, and no explanation of which of the six commands suits which intent — the examples only ever show 'ls' and a truncated 'cat'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.