Skip to main content
Glama

Where my hug at? (checked live)

where_my_hug_verify

Verify picked Hugging Face models and datasets: drop missing IDs, flag license, gating, staleness and low use, size each model against your compute, and return a report with next actions.

Instructions

Step 3 of 3: checks every picked model and dataset id live on its hub, drops the ones that are not there, flags licenses, gating, staleness and low use, sizes each model against the compute (fits, a stretch that fits only quantized, or cloud, with who hosts it), marks picks the search didn't turn up as from memory, names every hub a pick is on, shows what it found that wasn't picked, and returns the report to show the user. If nextAction is SEARCH_FIRST or RECALL_REPLACEMENTS, do what its instructions say and call again.

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

Input Schema

NameRequiredDescriptionDefault
needYesThe ML need in plain words: what goes in, what should come out, and what it is for
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
componentsYes
recommendationNoWhat to act on first: the one or two picks worth trying now and why (fit, license, use), then the ones to skip and why. Shown last, as "Start here"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / recommendation
      Added value: +{
      +  "description": "What to act on first: the one or two picks worth trying now and why (fit, license, use), then the ones to skip and why. Shown last, as \"Start here\"",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that missing ids are dropped, licenses/gating/staleness/use are flagged, sizing tiers (fits / quantized / cloud) are produced, memory-sourced picks are marked, and a report is returned. It omits auth, hub-access or rate-limit behavior, which keeps it from a 5.

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?

It is front-loaded with the useful 'Step 3 of 3' anchor, but the body is a single run-on sentence piling clause upon clause. Most clauses add information, yet the density hurts readability and the retry guidance would read better as a separate sentence.

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 no-annotation, no-output-schema tool it covers the essential ground: what it verifies, what it flags, what it sizes, and what it returns plus the follow-up call loop. A short note on what the returned report contains would complete it.

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 75%, so baseline is 3, and the description adds real meaning beyond the schema: it explains that compute is used to size each model ('sizes each model against the compute') and that recommendation surfaces as 'Start here' shown last. It leaves 'need' and 'components' semantics largely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('checks every picked model and dataset id live on its hub') and situates itself as 'Step 3 of 3', distinguishing it from where_my_hug_search and where_my_hug. An agent can tell exactly what this does without inspecting the schema.

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?

The 'Step 3 of 3' framing plus the nextAction retry instructions give clear sequencing guidance, and the SEARCH_FIRST/RECALL_REPLACEMENTS loop tells the agent what to do on each outcome. It never names the sibling tools as alternatives, so exclusions are implied rather than explicit.

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