Skip to main content
Glama

search_models

Finds Hugging Face video models compatible with your GPU, hiding models too large for your hardware. Leave the query empty to list LTX-Video and Wan VACE options.

Instructions

Searches Hugging Face for video models that fit this PC's graphics card (bigger ones are hidden). These are NOT tested by us; check_model reads a file's header first. Empty query = LTX-Video and Wan VACE models.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and the read/destructive hints, so the safety profile is covered. The description adds real context beyond that: results are hardware-filtered so the list is deliberately incomplete, and the models are untested third-party artifacts that should be vetted with check_model. It doesn't mention rate limits or result shape, keeping it at 4.

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 tight sentences, with the core purpose front-loaded and the caveat and default behavior following. The parenthetical GPU filter is efficient, though the second sentence packs three distinct ideas (trust, validation tool, empty-query default) rather densely.

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 single-parameter, no-output-schema search tool the description covers purpose, filtering, trust caveat, and default behavior. It omits how results are returned (model identifiers, metadata fields) and any result-count or paging limits, which an agent needs to consume the output correctly.

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 coverage is 0% for the single 'query' parameter, so the description must compensate; it does partially by defining the empty-string semantics as a curated default set. It never says what a non-empty query matches against (model name, task, tag), leaving the main parameter's matching behavior ambiguous.

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 (searches Hugging Face for video models) plus a meaningful scope constraint: only models that fit this PC's GPU, with larger ones hidden. It does not explicitly distinguish itself from the sibling 'list_models', which an agent could reasonably confuse it with, so it stops short of 5.

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?

Gives a clear follow-up path ('check_model reads a file's header first') and documents the zero-input default ('Empty query = LTX-Video and Wan VACE models'), which tells the agent what happens on the no-arg path. It stops short of explicit when-not guidance or naming list_models as the alternative.

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