Skip to main content
Glama

List LoRAs

list_loras
Read-only

Platform LoRAs (styles and looks) that generate and estimate_cost accept in loras. Each has a slug, a family matching a model's lora_family in list_capabilities, trigger words added to the prompt, and a default and max scale. Pass model (e.g. "z-image-turbo") to see only the LoRAs that model can use.

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_loras"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
familyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds real behavior: each entry carries a slug, a family keyed to `lora_family` in `list_capabilities`, trigger words injected into the prompt, and default/max scale. That cross-reference to another tool's field is the kind of context annotations cannot express, though a return schema already exists so some of this is duplicated.

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?

Three dense but well-ordered sentences: identity and consumers first, record shape second, filtering last. No filler, though the record-shape sentence packs several concepts into one clause chain and the `family` gap suggests space was misallocated.

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 two-parameter, optional-filter, read-only listing tool with an output schema, the description supplies the essential relational context (who consumes these values, how family maps to model capabilities) and one filter's usage. The unaddressed `family` input is the only material hole.

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 description coverage is 0%, so the description must carry the parameter burden. It does this well for `model` with an example value, but `family` is never mentioned as an input — the description explains the concept of a family only in the context of returned records, leaving the agent to guess that it is also a filter.

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 resource (platform LoRAs / styles and looks) and its role: the values that `generate` and `estimate_cost` accept in their `loras` argument. Naming the consuming siblings makes the tool distinguishable from `list_capabilities` and the other `list_*` tools without opening a 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?

Gives a concrete usage cue — pass `model` (e.g. "z-image-turbo") to narrow results to what that model supports — and implicitly tells the agent to call this before `generate`/`estimate_cost` when a LoRA is needed. It does not say when not to use it or how the `family` filter relates, leaving one branch to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources