Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hugging Face kernel

hugging_face_kernels_get
Read-onlyIdempotent

Retrieve a Hugging Face compute kernel by repository owner and name so coding agents can inspect kernel details and apply them in their workflows.

Instructions

Get a Hugging Face compute kernel. Requires 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": {
      "owner": "<owner>",
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_kernels_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.
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, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no note on what a kernel record contains, whether auth is needed for private repos, or any lookup failure behavior.

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 definition is short and front-loads the core purpose, but the second sentence merely repeats the schema's required fields, so it does not earn its place. Size is appropriate; content is partly redundant.

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 getter with full schema coverage and annotations, the essentials are present. However, with no output schema, the description gives no hint of what the returned kernel data looks like or how identifiers are formatted, leaving a modest 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 description coverage is 100%, so the schema fully documents owner, name, context, llm_model and conversation_id, including the conversation_id chaining rule. The description only restates that owner and name are required, adding no meaning beyond the schema; 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?

The description names a specific verb and resource ('Get a Hugging Face compute kernel'), which is enough to tell it apart from the sibling search tool by intent, though it never explicitly contrasts the two. The term 'kernel' is left undefined, but the resource is identifiable.

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?

There is no guidance on when to use this versus hugging_face_kernels_search, no prerequisites, and no statement that the identifier must already be known. At best 'Requires `owner` and `name`' hints that exact identifiers are needed, which is weak implied guidance.

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