Skip to main content
Glama

Ask the Antigravity agent (new conversation)

agy_ask_new

Starts a fresh agent conversation without prior context for a question, while keeping the previous default conversation alive so it can be resumed later.

Instructions

Same as agy_ask but starts a fresh conversation with no prior context. The previous default conversation stays alive and can be resumed with agy_resume.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "agy_ask_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoAgent execution mode (default: AGY_MODE).
modelNoModel id, see agy_models (default: AGY_MODEL).
effortNoReasoning effort (default: AGY_EFFORT).
timeoutNoTurn timeout in seconds (default: AGY_ASK_TIMEOUT).
questionYesThe prompt/question for the agent.
workspaceNoDirectory for the agent to work in (default: AGY_WORKSPACE or the server cwd).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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. It usefully discloses state semantics that the schema cannot: the previous default conversation remains alive and is resumable via agy_resume. However, it says nothing about whether the agent can modify files (relevant given the accept-edits mode option), that a new conversation record is created, or what state the caller must track to resume the new conversation later.

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?

Two short sentences, zero filler, with the primary differentiator (fresh conversation, no prior context) front-loaded before the follow-on state information. Nothing is redundant with the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter agent-spawning tool with no annotations and no output schema, the description covers the conversation-lifecycle semantics but omits what the call returns (e.g., a conversation id) and how the caller later addresses this new conversation, which matters given agy_resume exists. It is adequate but leaves real gaps for a tool of this complexity.

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 description coverage is 100%, so all six parameters including defaults and enums are already documented in the schema; baseline would be 3. The description adds a small amount of meaning by characterizing the call as starting a fresh conversation, which contextualizes the mode/workspace params, but it does not elaborate on any parameter's behavior.

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?

The description gives a concrete behavioral distinction: it "starts a fresh conversation with no prior context" versus agy_ask, and names agy_resume as the way back. The purpose is partly defined by reference to agy_ask ("Same as agy_ask but..."), so an agent must know the sibling to fully understand what it does, but the differentiating clause is specific enough to select between them.

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?

It clearly signals when to prefer this tool (you want a clean-slate conversation with no prior context) and names the alternative path (agy_resume) for the opposite need. There is no explicit when-not or statement about what agy_ask does differently beyond context inheritance, but the routing decision is clear.

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