Skip to main content
Glama

list_gemini_models

Read-only

Lists the Gemini model IDs accepted by the model and models parameters so you can choose a valid model for requests.

Instructions

List the model IDs accepted by the model / models parameters (runs agy models).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, environment-dependent read. The description adds that it shells out to `agy models`, which hints the list reflects whatever the local CLI knows about, but it does not say whether results are cached, network-dependent, or how they are formatted.

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?

A single tight sentence with the resource scope front-loaded and the parenthetical command detail trailing as supporting context. Nothing is redundant and nothing needs to be re-read.

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 parameterless listing tool with no output schema, the description covers what is returned (model IDs) and why it matters. A brief note on the return shape (e.g. a list of strings) or on whether the list is exhaustive for the current installation would have made it complete.

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?

There are zero input parameters, so the baseline is 4. The description still adds value by explaining that the returned identifiers are exactly the values accepted by the `model` / `models` parameters of other tools, which is meaning beyond an empty schema.

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 ('List') and a precise resource ('model IDs accepted by the `model` / `models` parameters'), plus the underlying invocation ('runs `agy models`'). This is clearly distinct from every sibling (ask_gemini, gemini_patch, gemini_review, gemini_task, read_gemini_log), none of which enumerate models.

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?

By tying the output to the `model` / `models` parameters, the description implies the correct use case: call this to discover a valid model ID before invoking a sibling that accepts one. It does not state exclusions or explicitly say 'call this before ask_gemini', so it falls short of a full when/when-not statement.

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