Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face inference models

hugging_face_inference_providers_models_list
Read-onlyIdempotent

Lists Hugging Face models served by inference providers, with optional filtering by model ID text or provider name, so you can find available models and the providers that host them.

Instructions

List the Hugging Face models that inference providers host. Optional inputs: query and provider. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_inference_providers_models_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOnly models whose id contains this text.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
providerNoOnly models this provider serves.
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, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only 'Returns a list,' which conveys nothing about ordering, pagination, or result size beyond the annotations. It also says nothing about the required session parameters (context, llm_model, conversation_id) that the schema documents.

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 core scope front-loaded and no filler. The brevity is efficient, though the second sentence ('Optional inputs... Returns a list') is largely redundant with the enumerated schema.

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?

For a simple read-only list operation with a 100%-documented schema and full annotations, minimal description is defensible. However, the tool has five parameters including required analytical/session fields, and the description accounts for none of them or for the return shape, leaving the definition only barely adequate.

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%, so both 'query' and 'provider' are already fully explained as filters. The description merely restates that these inputs are optional and adds no filter syntax, matching behavior, or interaction detail beyond 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?

A specific verb and resource: 'List the Hugging Face models that inference providers host' scopes the list to provider-hosted inference models, which is more precise than a bare 'list models'. It does not name or distinguish itself from close siblings such as hugging_face_models_search or hugging_face_models_get, so an agent must infer that difference.

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 guidance is that 'query' and 'provider' are optional inputs, which is already visible in the schema. There is no statement of when to use this instead of hugging_face_models_search or hugging_face_models_get, 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.

Deploy Server

Other Tools