Skip to main content
Glama

hf_search

Search Hugging Face Hub for models or datasets by query, returning the most downloaded matches first to help you choose resources for GPU training and inference.

Instructions

Search the Hugging Face Hub for models or datasets, most downloaded first.

kind: "model" or "dataset".

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>"
    },
    "name": "hf_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNomodel
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose one real behavioral trait beyond the schema — results are ranked by download count — but it says nothing about authentication requirements, result pagination behavior, rate limits, or what happens with an empty query.

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 lines with the core action and sort order front-loaded and no filler. The trailing 'kind: "model" or "dataset"' snippet is terse to the point of looking like a schema fragment, but it earns its place by documenting an otherwise undocumented parameter.

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

Completeness5/5

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

An output schema exists, so return values need not be described. For a three-parameter read-only search, the definition covers the action, resource, sort behavior, and the key enum-like parameter; the remaining gaps (auth, pagination) are minor for this complexity level. Score reflects relative adequacy, with the missing limit explanation the only notable omission.

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 0%, so the description must compensate. It partially does by explaining the 'kind' parameter's two accepted values ('model' or 'dataset'), but leaves 'query' semantics (matching behavior, minimum length) and 'limit' (beyond the default of 10) entirely unexplained.

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 ('Search the Hugging Face Hub for models or datasets') and adds the sort order ('most downloaded first'), which lets an agent distinguish it from fetch-oriented siblings like hf_download or hf_push_run. It does not explicitly name a competing discovery tool, so it stops short of 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?

Usage is only implied: a search tool that ranks by downloads is clearly a discovery/lookup step, presumably before download or run. There is no statement of when to prefer it over alternatives such as kaggle_search_datasets, and no prerequisites or exclusions are given.

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