Skip to main content
Glama

List models

list_models
Read-only

The catalog's models with each provider's offering, price, capabilities and quality scores, filtered by task, providers and needs. Returns 20 models unless limit says otherwise; page with offset. Counts as one call.

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
taskNoOnly models for this task.
limitNoPage size, 1–500 (default 20).
needsNoOnly offerings with these capabilities. Comma-separated.
offsetNoModels to skip (default 0).
providersNoOnly offerings on these providers. Comma-separated.
include_hiddenNoInclude offerings that are never recommended (default false).
include_retiredNoInclude retired offerings (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a default result count of 20, the limit override, offset-based paging, and the billing note 'Counts as one call', which an agent cannot derive from structured fields.

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?

Two sentences, zero filler, front-loaded with what is returned before the pagination and cost caveats. Every clause carries distinct information: contents, filters, default size, paging, and call accounting.

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?

With no output schema, the description usefully enumerates the returned fields (offering, price, capabilities, quality scores) and covers default page size and paging. The only gap is that default exclusion of hidden and retired offerings is left entirely to the schema, so an agent skimming the prose may not realize results are filtered by default.

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%, so every parameter including limit, offset, needs, providers and the hidden/retired flags is already documented. The description only restates the task/providers/needs filters and the default of 20 results, adding little syntax or semantic detail beyond the schema — 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 states a concrete resource and its contents: 'the catalog's models with each provider's offering, price, capabilities and quality scores', plus the filtering dimensions. It is clear this is a multi-model catalog listing rather than a single-record fetch like get_model, though it never explicitly names that sibling to sharpen the distinction.

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

Usage Guidelines3/5

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

Usage is implied through the filter and pagination guidance ('filtered by task, providers and needs', 'page with `offset`'), which tells the agent how to narrow and page. There is no explicit when-to-use versus when-not statement, and no named alternative such as get_model for single-model lookups, so the agent must infer routing.

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