Skip to main content
Glama

List Claude models and when to use each

list_models

Returns a guide for each Claude model with API IDs and suitable tasks, helping you select the right model for a job.

Instructions

Returns the model guide: each Claude model, its API id, and what it is best for.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose what the call yields (model guide entries with API ids and best-for notes), which implies a safe read-style lookup. It does not say whether the guide is static or live, how it is formatted, or roughly how many entries come back, leaving the shape of the response to be discovered at call time.

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?

One sentence, front-loaded with the action and the returned content, with zero filler or repetition of the title. Every clause earns its place by naming a distinct field in the result.

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-parameter reference tool with no output schema, the description covers the essentials of what comes back at a summary level. The only real gap is the exact structure/format of the returned guide, which the agent must learn from the first call.

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, so the baseline is 4 and there is nothing for the description to disambiguate. The description correctly presents this as an unfiltered, argument-free call rather than hinting at optional filters that do not exist.

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 ('Returns') and a specific resource ('the model guide') and enumerates its contents: each Claude model, its API id, and its best use. The purpose is unambiguous, though it never contrasts itself with the sibling recommend_model, so an agent must infer the lookup-vs-recommendation split.

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 only implied: the phrase 'what it is best for' suggests consulting this before picking a model, but there is no explicit when-to-use, no when-not-to-use, and no pointer to the alternatives recommend_model or review_model_choice. An agent would likely guess correctly, but the description does no routing work.

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

Deploy Server

Other Tools