lmstudio

LM Studio: list models

list_models

Read-only

Retrieve downloaded LM Studio models with key, type, size, quantization, max context, capabilities, loaded instances, and saved defaults; filter by type or loaded status.

Instructions

List the models downloaded to LM Studio with key, type, size, quantization, max context, capabilities, loaded instances and saved defaults.

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

Input Schema

Name	Required	Description	Default
`type`	No	Filter by model type. Default: all.
`loaded_only`	No	Only models that are loaded right now.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description goes beyond them by enumerating exactly what comes back: key, type, size, quantization, max context, capabilities, loaded instances and saved defaults. That return-shape disclosure is genuinely useful given there is no output schema. It stops short of 5 because pagination, ordering, or error behavior are not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; the field enumeration is dense but every item earns its place by substituting for a missing output schema.

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 read-only, two-parameter listing tool with no output schema, the description supplies the one thing the structured data lacks: the set of fields returned. Nothing essential to calling it correctly is missing, though a note on result ordering or behavior when no models are installed would make it complete.

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 100%, with both parameters (type enum, loaded_only boolean) fully documented in the schema, so the schema already carries the burden. The description adds no extra meaning about how 'loaded instances' relates to the loaded_only filter or what 'saved defaults' means when filtering. 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 opens with a specific verb and resource ('List the models downloaded to LM Studio') and scopes it to downloaded models, which implicitly separates it from download_model and load_model. It falls short of 5 because it never names a sibling or explicitly contrasts behavior with one.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the inventory-listing call to make before load/unload/chat decisions. There is no explicit statement of when to prefer it over a sibling (e.g. loaded_only vs. a load-status call) and no exclusions or prerequisites.

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