Skip to main content
Glama

list_models

Read-onlyIdempotent

List LLM and related models available to this workspace (current Fast / Balanced / Capable per provider, plus evaluation models). Omit modality for language and evaluation; pass "evaluation", "image", "video", or "all" to narrow. Use when choosing a model for create_agent or update_agent (provider "gateway", model id from this list).

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
modalityNoFilter by model type. Omit to list language and evaluation models. Pass "evaluation", "image", "video", or "all" to narrow.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and idempotentHint, so safety is covered. The description adds real behavioral context beyond them: the default result set when modality is omitted, and the fact that results are per-provider with Fast/Balanced/Capable tiers. It does not describe ordering or how the list changes, which keeps it below a 5.

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?

Two tight sentences, front-loaded with the purpose before the filtering and usage guidance. Minor waste in repeating the modality default that the schema already spells out verbatim.

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 zero-required-parameter read-only listing tool with a fully documented single enum parameter, the definition covers what the agent needs, including the downstream consumer of the results. Only the exact result shape/ordering is unspecified, and there is no output schema to lean on, but that is a minor gap.

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 schema already documents the modality enum and its default behavior, so the description's filter sentence largely restates it. Baseline 3 is appropriate; no extra meaning (such as what happens with "all" plus a provider) is added here that the schema lacks.

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 verb and resource ("List LLM and related models available to this workspace") and scopes the result set: current Fast/Balanced/Capable per provider plus evaluation models. An agent can immediately tell this apart from list_agents, list_tools, and other listing siblings.

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 when-to-use: choosing a model for create_agent or update_agent, and even names the provider value ("gateway") and that the model id comes from this list. It never says when not to call it or what to do if the needed model is absent, so it falls short of full alternative/exclusion guidance.

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