Skip to main content
Glama

codex_models

Read-onlyIdempotent

Discover available model IDs, supported reasoning efforts, and defaults to choose an appropriate model for a coding task. Catalog visibility does not guarantee entitlement.

Instructions

Discover model ids, supported reasoning efforts and defaults. Catalog visibility is not an entitlement guarantee.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNoNative cursor

Output Schema

NameRequiredDescriptionDefault
okYes
result_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds one genuinely non-obvious behavioral note — that catalog visibility does not imply entitlement — which matters because results can include unusable models. It does not mention pagination behavior despite limit/cursor parameters.

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 short, front-loaded sentences with no filler; the capability statement comes first and the caveat second. Nothing is padded, though the caveat could be slightly more explicit about what an agent should do when a model is listed but not entitled.

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?

An output schema exists, so return values need no explanation, and the tool is simple. Still missing is any indication of result size, paging usage, or how this differs from sibling discovery tools, which for an open-world catalog lookup leaves a modest gap.

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?

Only two parameters, and 'cursor' is documented in the schema as the native cursor; 'limit' carries default=100, min=1, max=200. The description adds nothing parameter-specific, but with this little parameter surface and partial schema coverage, there is minimal meaning left to convey.

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?

States a specific verb ('Discover') and concrete resources: model ids, supported reasoning efforts, and defaults. An agent can tell this is a catalog-introspection tool, distinct from status or session tools, though it never explicitly contrasts itself with the similarly named codex_capabilities or codex_settings.

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 or when-not guidance and no named alternative, so an agent must infer that this is the pre-flight lookup for model selection. The second sentence is a result-interpretation caveat, not routing guidance.

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