Skip to main content
Glama

Discover Codex models and effort levels

models_list
Read-onlyIdempotent

Fetches the current Codex model catalog with descriptions, default model, effort options, and package update status before choosing a model; runs no inference and does not confirm account access.

Instructions

Call first to fetch the current Codex model catalog with descriptions, default model, default effort and supported effort descriptions. No inference is run. Catalog entries do not guarantee account/provider inference access. Includes package update status; relay an available update once per newer version per session in the user language. Updating and reconnecting are user actions.

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": "models_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeHiddenNoInclude models hidden from the default picker.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description explicitly discloses operational behaviors like including 'package update status' and the specific mechanism of relaying updates ('once per newer version per session in the user language'), adding practical, non-structural context.

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?

While slightly dense, the structure is highly effective. Every clause conveys vital information—from safety (no inference) to operational constraints (updates)—meaning no sentence is truly wasteful.

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?

Given that the tool is a read-only list (reinforced by annotations), the description is maximally complete by addressing what the list contains, operational prerequisites, and what it doesn't guarantee (like provider inference).

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?

The schema provides 100% coverage for the single parameter 'includeHidden'. The description does not add specific semantic meaning or formatting constraints to this parameter, making the baseline score appropriate.

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?

The description clearly states the function is to 'fetch the current Codex model catalog' and specifies exactly what information is contained within that catalog, including descriptions, default model/effort, and package status.

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

Usage Guidelines5/5

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

It provides crucial guidelines: 'Call first' (implying setup order), 'No inference is run' (managing agent expectations), and specifies that 'Updating and reconnecting are user actions,' effectively defining the tool's operational role and boundaries.

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