Skip to main content
Glama

claude_models

Lists available EnMaaS and GCP Vertex AI models with cost and tier tags so you can inspect supported options before generating a Claude command.

Instructions

List available models for Red Hat EnMaaS AI Gateway and GCP Vertex AI projects with cost and tier tags. INSTRUCTION: Call this tool FIRST to inspect supported models before generating a command with claude_prompt. Returns real-time models for EnMaaS (free GLM 5.3) and supported canonical Claude models (sonnet, opus, haiku, claude-sonnet-5, claude-opus-4-8) per Vertex AI project.

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

Input Schema

NameRequiredDescriptionDefault
projectNoFilter for a specific GCP Vertex AI project ID.
providerNoProvider filter: "enmaas", "vertex", or "all" (default).all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the disclosure burden, and it does useful work: it says results are real-time, that entries carry cost and tier tags, and it names concrete model examples (free GLM 5.3, sonnet/opus/haiku variants). It is silent on authentication prerequisites, latency, and failure behavior when a project has no models.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the routing instruction follows logically, but the parenthetical enumeration of model names ('sonnet, opus, haiku, claude-sonnet-5, claude-opus-4-8') is low-value clutter, and the 'INSTRUCTION:' label is heavy-handed phrasing for what is ordinary usage guidance.

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 two-parameter, optional-parameter listing tool with no output schema and no annotations, the description covers purpose, routing, providers, and the shape of returned data (models with cost and tier tags) well enough to invoke it correctly. Missing only edge-case behavior and reconciliation of the 'auto' provider value.

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 coverage is 100%, so both parameters are already documented, and the description only adds the notion that models are scoped 'per Vertex AI project'. Notably it describes the provider filter as "enmaas", "vertex", or "all", omitting the schema's real 'auto' enum value, which slightly undercuts rather than clarifies parameter semantics.

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?

States a specific verb and resource (list available models) plus the two providers covered (EnMaaS gateway, GCP Vertex AI projects), and explicitly separates itself from the sibling claude_prompt by framing itself as the inspection step that precedes prompt generation.

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?

The 'Call this tool FIRST ... before generating a command with claude_prompt' line gives explicit ordering guidance and names the alternative tool. It lacks any when-not-to-use condition (e.g., cached results, or when the project is already known) and gives no advice on choosing between the provider filters.

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