Skip to main content
Glama
gregpriday

Ask Google MCP Server

by gregpriday

ask_google

Read-onlyIdempotent

Retrieve up-to-date answers about versions, releases, API changes, and breaking news by combining Gemini with Google Search grounding.

Instructions

Gemini with Google Search grounding. Use for current/latest facts that post-date your training: versions, releases, API changes, changelogs, breaking news, on-demand web research. Do not use for stable syntax or knowledge already in your training. Short lookups or multi-paragraph briefs both work.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoGoogle model. 'auto' (default, recommended) picks the right tier automatically. Override with 'flash' or 'flash-lite' only if you need a specific one.auto
queryNoAlias for `question`. Accepted for compatibility with callers that use the name `query`; prefer `question`. Do not set both at once.
questionNoYour question for the AI researcher. Short lookups or multi-paragraph research briefs both work. Prefer 'current/latest/as of today' over hardcoding dates unless a specific historical year matters. `query` is accepted as an alias.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
answerYes
sourcesNo
supportsNo
diagnosticsNo
search_queriesNo
grounding_statusNoHow thoroughly the answer is grounded. 'grounded' = sources + per-claim supports. 'sources_only' = pages retrieved but no per-claim mapping. 'no_sources' = search ran but returned nothing — answer is from training data, treat with high skepticism. 'not_attempted' / 'unavailable' = even worse.
answer_with_citationsNo
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds context about using Gemini with Google Search grounding and the nature of queries. No contradiction with annotations.

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?

Description is brief (3 sentences), front-loaded with purpose, and every sentence adds value. No unnecessary words or repetition.

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?

Given no sibling tools, rich annotations, full schema coverage, and presence of output schema, the description is complete. It covers when to use, when not to use, and the nature of the tool without omissions.

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% with detailed descriptions and examples for both parameters. The description adds only a minor note that queries can be short or long, but the schema already covers parameter semantics adequately. Baseline 3 applies.

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 is for current/latest facts post-dating training, listing specific use cases like versions, API changes, and breaking news. It distinguishes itself from general knowledge by explicitly stating what not to use it for.

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?

Explicitly provides when to use (current topics) and when not to use (stable syntax, training knowledge). Also mentions both short lookups and multi-paragraph briefs are acceptable, offering clear guidance on usage scenarios.

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/gregpriday/ask-google-mcp'

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