Skip to main content
Glama

Ask agy (Antigravity/Gemini)

agy_ask

Send a prompt to the agy CLI and receive a response from Gemini models. Use for model queries, delegation, or continuing conversations.

Instructions

Send a prompt to the agy CLI (Antigravity, Gemini-backed) and return its response.

Runs agy non-interactively in print mode. Use this for a second opinion from Gemini/Claude/GPT models, to delegate a self-contained task, or to continue a multi-turn agy conversation.

Args:

  • prompt (string, required): The prompt to send.

  • model (string, optional): A model from agy_list_models (e.g. "Gemini 3.1 Pro (High)"). Omit for default.

  • add_dir (string[], optional): Absolute dirs to add to agy's workspace so it can read those files.

  • project (string, optional): Existing agy project ID.

  • new_project (boolean, default false): Create a new project for this session.

  • continue_conversation (boolean, default false): Continue the most recent conversation.

  • conversation_id (string, optional): Resume a specific conversation by ID (overrides continue_conversation).

  • timeout_ms (number, default 300000): Max wait in ms (1000..1800000).

Returns JSON: { "response": string, "model": string, "exit_code": number }. On failure exit_code is non-zero and response contains agy's stderr (e.g. binary not found, timeout).

Note: runs agy with --dangerously-skip-permissions so tool actions inside agy are auto-approved (required for non-interactive use). Only invoke with prompts you trust to run unattended.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel name from agy_list_models (e.g. 'Gemini 3.1 Pro (High)'). Omit for the CLI default.
promptYesThe prompt to send to agy.
add_dirNoAbsolute directory paths to add to agy's workspace so it can read those files while answering.
projectNoExisting agy project ID to run the session under.
timeout_msNoMax time to wait for agy to respond, in milliseconds (default 300000 = 5m).
new_projectNoCreate a new agy project for this session instead of using the default/most-recent.
conversation_idNoResume a specific prior conversation by its ID. Takes precedence over continue_conversation.
continue_conversationNoContinue the most recent agy conversation (adds turns to it) instead of starting fresh.
Behavior4/5

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

Annotations indicate read/write and open world. The description adds key behaviors: non-interactive mode, use of --dangerously-skip-permissions, auto-approval of tool actions, and failure modes (binary not found, timeout). This exceeds annotation information.

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?

The description is well-structured: first sentence states purpose, then bullet arguments, return format, and a crucial note. Every sentence adds value with no redundancy.

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?

With 8 parameters and no output schema, the description covers all parameters, return format, and error handling. However, lacking details on how to obtain project IDs or the exact workspace behavior limits completeness slightly.

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?

Schema coverage is 100% with descriptions. The description's Args section adds context (e.g., 'absolute dirs to add to agy's workspace'), improving understanding beyond the schema alone.

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?

The description clearly states the tool sends a prompt to the agy CLI and returns its response, and it distinguishes this from sibling tools (auth, list models) by specifying use cases like second opinion, delegation, and conversation continuation.

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?

Explicitly mentions when to use (second opinion, delegate task, continue conversation) and implies caution due to auto-approval, but does not explicitly state when not to use or list alternatives beyond siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yinjs/agyenvoy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server