Skip to main content
Glama

List AI models

list_ai_models
Read-only

The model catalog the organisation's chat picker offers (the twin of ankra ai models list): each model's key, tier, context window, output limit, whether it supports tools, thinking and images, and whether it is enabled or the default. Use this to answer 'which models can I use' or to explain why a model cannot run tools. Read-only; catalog edits are portal or CLI lanes.

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_ai_models"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only; catalog edits are portal or CLI lanes', which usefully tells the agent not to look for a write path. It also discloses the shape of what is returned (capability flags, enabled/default status), which is above the annotation baseline, though it says nothing about result size, ordering, or whether disabled models are included.

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?

Three sentences, front-loaded with the resource and its returned fields, then the use cases, then the read-only scope note. Nothing is repeated from the title or annotations verbatim, and the parenthetical CLI twin is short enough to be a useful anchor rather than clutter.

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?

With zero parameters and no output schema, the description carries the full burden and meets it by enumerating the returned fields and stating org scoping ('the organisation's chat picker'). An agent can call this tool and interpret the result without further information.

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?

The tool takes zero parameters, which is the baseline-4 case; there is no parameter semantics to add. The description does compensate by describing the output fields, which no schema documents since there is no output schema.

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+resource ('the model catalog the organisation's chat picker offers') and enumerates exactly what each entry contains (key, tier, context window, output limit, tool/thinking/image support, enabled/default flags), so an agent knows precisely what comes back. It stops short of naming the near-neighbour siblings (get_ai_environment, get_ai_settings) to disambiguate from them explicitly.

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?

It states concrete invocation triggers — 'which models can I use' and 'explain why a model cannot run tools' — which map to real questions an agent will face. It also closes off a tempting misuse by saying catalog edits live in the portal or CLI, though it does not point at any specific alternative tool for AI-environment/settings questions.

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.