Skip to main content
Glama

List Brennglas models

list_models

Lists local image and video models, their modes, workflows, and input field details so you can choose a runnable model and pass valid options before rendering.

Instructions

Lists the local image and video models with their modes, the workflow name per mode, and every input field (type, default, range, options). Call this first. Enum options can be passed by their shown name (e.g. camera "Arc left"). Models with "missing" files cannot run.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does useful work: it states the models-with-missing-files cannot run (a hard precondition the agent would otherwise discover only at failure time) and explains how to pass enum options. It does not state cost, latency, or explicitly that the call is side-effect free, though "Lists" strongly implies read-only.

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?

Four short sentences, front-loaded with what is returned, followed by the one action instruction and two caveats. No filler, and the most decision-relevant line ("Call this first") is placed early.

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

Completeness5/5

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

No output schema exists, so the description must describe return values, and it does so precisely: models, modes, workflow name per mode, and each input field with type, default, range, and options. Combined with the missing-files warning and enum-passing rule, an agent has everything needed to call it and interpret the result.

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?

There are zero input parameters, so the baseline is 4. The description goes slightly beyond by explaining how returned enum options should be supplied back on later calls ("can be passed by their shown name"), which is genuinely useful semantics for a parameterless discovery tool.

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?

"Lists the local image and video models with their modes, the workflow name per mode, and every input field" names a specific verb and resource and enumerates the returned structure. An agent can distinguish it immediately from siblings like generate, concat, or gallery, which operate on media rather than enumerating model metadata.

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?

"Call this first" gives an explicit ordering instruction that tells the agent when to reach for this tool before others. It stops short of naming any alternative or exclusion case, but for a zero-parameter discovery tool the sequencing guidance covers the main decision an agent faces.

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