Skip to main content
Glama

Get Available Models

get_available_models

Retrieve all available AI models with their specifications, limits, defaults, and features so you can select the right model for text-to-image, video, audio, and transcription tasks.

Instructions

Get list of available AI models with detailed specifications.

Retrieves all available models for different inference types (txt2img, txt2video, img2img, img2video, audio_file2text, img2txt, video2desc, etc.) along with their capabilities, limits, defaults, and features.

IMPORTANT - How to use model specifications:

Each model's 'info' field contains critical information you MUST check before using:

  1. inference_types: List of supported operations (e.g., ["txt2img", "img2img"])

  2. info.limits: Min/max constraints for ALL parameters. Examples:

    • max_guidance/min_guidance: Valid range for guidance_scale

    • max_steps/min_steps: Valid range for inference steps

    • max_width/min_width, max_height/min_height: Image/video dimensions

    • max_frames/min_frames: Number of video frames

    • max_fps/min_fps: Video frame rate

  3. info.defaults: Recommended default values for the model. Examples:

    • If defaults.guidance="0", use guidance_scale=0

    • If defaults.steps="1", use steps=1

    • Use these when model has specific requirements

  4. info.features: Boolean flags (0=false, 1=true) indicating support:

    • supports_steps: If "0", model has fixed steps

    • supports_negative_prompt: If "0", don't pass negative_prompt

    • supports_last_frame: If "1", img2video supports initial frame control

    • supports_voice_clone / supports_voice_design / supports_custom_voice: which TTS mode the model implements. It implements exactly one and returns 422 for the others

    • supports_guidance: no model in the catalogue currently sets this to "1", so leave guidance unset and the model's own default is used

    • supports_image_refs / supports_video_refs / supports_audio_refs: img2video reference mode (ref_images / ref_videos / ref_audios); limits.max_ref_* give the counts, 0 meaning that type is not taken

    • supports_presets: video description presets, listed in limits.available_presets

General rule: rather than assuming a value, omit the parameter and let the model's info.defaults apply, or read the bound from info.limits.

Example workflow for txt2video with LTX-Video model:

  1. Check inference_types includes "txt2video"

  2. Check limits.max_steps = "1" → must use steps=1

  3. Check limits.min_fps = "30", max_fps = "30" → must use fps=30

  4. Use defaults for other parameters (width=512, height=512, frames=120)

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": "get_available_models"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A3.9/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 add real behavioral context: features are boolean 0/1 flags, TTS models implement exactly one voice mode and 'return 422 for the others,' supports_guidance is never set so guidance should be omitted, and limits.max_ref_* of 0 means that ref type is not accepted. It omits authentication, rate limits, and whether results are cached or static.

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 purpose is front-loaded and the numbered info.* sections are scannable, but the block is long and drifts into a user manual for downstream generation parameters, with some redundancy (the 'General rule' restates the omit-and-let-defaults-apply idea already implied). The worked LTX-Video example is illustrative but is the most expendable passage.

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?

An output schema exists, yet the meaning of the info.limits/defaults/features fields is not inferable from structure alone, and the description supplies exactly that interpretive layer plus the 422 constraint. For a zero-parameter discovery tool, an agent has what it needs to call it and use the result correctly.

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?

The tool takes no parameters, so the baseline is 4; the description correctly says nothing about inputs and instead spends its space on output semantics, which is the right allocation.

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 first sentence names a specific verb and resource: 'Get list of available AI models with detailed specifications,' and the second adds the scope (all inference types: txt2img, txt2video, audio_file2text, etc.). It is unmistakably the catalogue/discovery tool versus the generation and *_price siblings, though it never explicitly contrasts itself with them.

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?

'You MUST check before using' plus the numbered interpretation steps and the 'Example workflow for txt2video' establish a clear call-first sequence before invoking a generation tool. It stops short of naming an alternative tool or stating when NOT to call it, so the routing guidance is strong but implicit.

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