Skip to main content
Glama

list_models

Read-only

Lists installed and downloadable models with size, required graphics card, test status, and the best pick for your PC, plus the use_as value to pass to render(model=...).

Instructions

What models are installed and what can be downloaded, with size, the card they need, and if we tested them. "best" marks the best one for this PC's graphics card. Use a model's "use_as" value in render(model=...).

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.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavior: the result spans both installed and downloadable models, includes size, required card, and a tested flag, and annotates a "best" entry tuned to this PC's GPU. That is substantive context beyond the annotations, though performance/caching or pagination behavior is unmentioned.

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 short sentences, front-loaded with what the tool returns before moving to the "best" marker and the render hand-off. Every sentence carries information; the only slight weakness is the informal 'the card they need' phrasing where a precise term would be clearer.

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?

With no parameters and no output schema, the description must carry the return-value story, and it does: install state, downloadability, size, required card, test status, the "best" flag, and the use_as key needed by render. Nothing an agent needs to call this correctly or consume its output is missing.

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 zero parameters, so per calibration the baseline is 4; there is no parameter meaning the description needs to supply. It sensibly spends its text on output fields instead.

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 states concretely what the tool returns: installed models plus downloadable ones, each with size, required graphics card, and test status. The verb is implicit ("what models are installed") rather than a crisp 'list', and it does not distinguish itself from siblings like search_models or check_model, keeping it at 4 rather than 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?

It gives concrete downstream usage: take a model's "use_as" value and pass it to render(model=...). That is real when/how guidance, but it never says when to prefer this over search_models or when not to call it, so it stops short of full routing guidance.

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