Skip to main content
Glama

Where my hug at?

where_my_hug

Collect missing ML details before choosing a model or dataset, then split the need into parts and search Hugging Face and other hubs to decide what to use, fine-tune, train, or code.

Instructions

Step 1 of 3, before recommending any machine learning model or dataset. If compute, license, stack or data is missing, returns the questions to ask the user first: call again with the answers ("unknown" is fine). Then returns the method: split the ML need into parts, search Hugging Face and the other hubs for each with where_my_hug_search, and decide from what it finds which parts they cover (use a model as is, fine-tune one, train one) and which are plain code. Follow it.

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": {
      "need": "<need>"
    },
    "name": "where_my_hug"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoTraining data there is or could be, such as "none" or "about 300 labeled photos"
needYesThe ML need in plain words: what goes in, what should come out, and what it is for
stackNoWhat will call the model: language, runtime, framework
computeNoThe hardware it has to run or train on, such as "one 24 GB GPU" or "CPU only". Size flags take the first "N GB" in it as the memory a model must fit in
licenseNoWhat the result may be used for, such as "commercial, closed source" or "research only"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses conditional behavior: missing inputs produce clarifying questions, 'unknown' is acceptable, and the tool then returns a method rather than a final recommendation. It does not describe safety or statefulness, but it explains the interaction pattern and return content well.

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?

The description is front-loaded with the step and purpose, and every sentence contributes to the workflow. The long method sentence is dense but not padded, though it could be split for readability.

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

Completeness4/5

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

For a five-parameter planning tool with no output schema, the description explains the conditional return, the next search step, and how to use the result. It mentions step 1 of 3 but omits where_my_hug_verify, leaving a minor gap in the full workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds workflow meaning by naming the optional inputs (compute, license, stack, data), explaining that missing values trigger questions, and noting that 'unknown' is acceptable.

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 that this is step 1 of 3 before recommending an ML model or dataset, and that it returns either clarifying questions or a method to follow. It distinguishes itself from the search sibling by directing the agent to use where_my_hug_search for hub searches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It clearly says to use this before recommending any ML model or dataset, to call again with answers when compute, license, stack, or data is missing, and to use where_my_hug_search for the search step. It lacks an explicit 'when not to use' statement but gives strong sequencing and alternative guidance.

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