Skip to main content
Glama

List Models

list_models
Read-only

Retrieve available LLM models across OpenAI, Google, Groq, and Ollama, with optional fresh API fetching instead of cached configurations.

Instructions

List available models for LLM providers

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
providerNoProvider name (optional, lists all if not specified)
fetch_latestNoFetch latest models from API vs using cached/configured

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.20.14
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv1.19.6
  3. Removedv1.19.5
  4. Changed3 schema fields changedv1.2.3
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / provider / enum
      Added value: +[
      +  "openai",
      +  "google",
      +  "groq",
      +  "ollama"
      +]
  5. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-call behavior are covered structurally. The description adds nothing beyond that — it does not mention that listing may hit provider APIs, how caching affects freshness, or whether unavailable providers are filtered out. With annotations carrying the safety profile, this is a missed opportunity rather than a failure.

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 no filler. Every word earns its place, though the brevity is also the source of the gaps noted elsewhere.

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

Completeness3/5

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

For a two-parameter, zero-required read tool with full schema coverage and annotations, the description is minimally sufficient. It omits what the returned model list represents and how fetch_latest interacts with provider availability, which an agent would need to interpret results correctly.

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 100% and the enum on provider is self-explanatory, so the schema does the heavy lifting. The description adds no meaning beyond it, such as what 'configured' means for fetch_latest=false. 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 gives a specific verb (List) and resource (available models) scoped to LLM providers, which cleanly separates it from the duck-conversation siblings. It stops short of saying whether the list reflects configured providers or all supported ones, but the core purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer cached versus freshly fetched models, and no reference to alternatives. An agent must infer from the parameter names alone whether to call this before ask_duck or chat_with_duck to discover valid model names.

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