Skip to main content
Glama

Google AI Answer

google_ai_answer
Read-onlyIdempotent

Asks Google AI Mode a question and returns the generated answer as markdown text plus up to 20 references (title, url, source). Use it for a summarized answer with its cited sources. Reference urls can be Google redirect links rather than publisher URLs. It does not return a ranked list of results (use google_search). Required: query.

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": {
      "query": "<query>"
    },
    "name": "google_ai_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesQuestion in natural language, 1-8000 characters, e.g. "How does an espresso machine build pressure?".
countryNoTwo-letter country code that localizes the answer and its sources, e.g. "it" or "gb". Omit for the source default, us.
languageNoTwo-letter language code for the answer, e.g. "en" or "it". Omit for the source default, en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter country code used to localize the answer."New value: +"Two-letter country code that localizes the answer and its sources, e.g. \"it\" or \"gb\". Omit for the source default, us."
    • changedInput schema / properties / language / description
      Previous value: -"Two-letter language code for the answer."New value: +"Two-letter language code for the answer, e.g. \"en\" or \"it\". Omit for the source default, en."
    • changedInput schema / properties / query / description
      Previous value: -"Question for AI-assisted search."New value: +"Question in natural language, 1-8000 characters, e.g. \"How does an espresso machine build pressure?\"."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish the read-only, idempotent, open-world profile, and the description adds genuinely new behavioral context: output is markdown, references are capped at 20, and reference URLs may be Google redirect links rather than publisher URLs. It stops short of covering failure modes or rate limits, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with what the tool returns, followed by the reference caveat, the sibling exclusion, and the required parameter. Every sentence carries distinct information with no filler.

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

Completeness5/5

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

With no output schema, the description compensates by describing the return payload (markdown answer plus up to 20 references with title, url, source) and its caveat about redirect links. Combined with a fully documented 3-parameter schema and safety annotations, an agent has everything needed to call it correctly.

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% and each parameter carries its own description, including examples and enum values, so the structured data does the heavy lifting. The description only repeats that 'query' is required and adds no syntax or localization guidance beyond the schema's own country/language notes.

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 states a specific verb and resource ('Asks Google AI Mode a question and returns the generated answer as markdown text plus up to 20 references') and explicitly separates itself from google_search. An agent can tell exactly what this tool produces without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names both the intended use ('Use it for a summarized answer with its cited sources') and the exclusion with an alternative ('It does not return a ranked list of results (use google_search)'). Nothing about when to prefer this tool is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources