Skip to main content
Glama

List Antigravity models

agy_models

Lists the model IDs supported by the installed agy CLI, using a five-minute cache to reduce repeated lookups.

Instructions

List the model ids the installed agy supports (cached 5 min).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so this description must carry the full burden of explaining behavior. It does add genuine value by disclosing that results are cached for 5 minutes, which warns of staleness; however, it says nothing about whether the cache can be invalidated, whether a newly installed model is visible immediately, or what happens if agy is not installed. That state is a real risk here, yet the description does not explain it.

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?

It is a single tight sentence with the caching constraint placed in parentheses so it does not obscure the main purpose. Nothing is padded.

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?

It is a simple, argument-free read tool with no output schema, and stating that it returns model ids covers the essential return information. The remaining gap is minor: it does not specify whether ids are plain strings or objects with metadata, and it does not describe error behavior when agy is missing.

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?

This tool has zero parameters, so there is no parameter semantics to document; the baseline of 4 applies.

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?

Names a specific verb and resource: listing the model ids that the installed agy supports. That is clearly distinct from the sibling operations (ask, conversations, resume, status, stop), though the description does not explicitly contrast itself with any of them.

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 explicit when-to-use guidance and no reference to alternatives, and the description never says to call this before agy_ask or agy_resume to obtain a valid model id. The only usage signal is the implicit fact that you fetch ids in order to pass them elsewhere.

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