Skip to main content
Glama

Google Search Grounded Real-Time Fact & Citation Engine

search_gemini_grounded_web
Read-onlyIdempotent

Answer factual queries with live Google Search grounding, returning verified answers plus source URLs and metadata. Use it to check current web facts, docs updates, or events in one call.

Instructions

Answers factual queries with live Google Search grounding, returning verified up-to-date answers accompanied by source URLs and grounding metadata. Use when verifying live web facts, documentation updates, or current events in a single low-latency call; for querying geographic places, coordinates, directions, and local business data via Google Maps grounding, use search_gemini_grounded_maps instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'prompt' ('recency_bias' defaults to 'past_24h'), supports '?demo=true' or L402 (75 sats), and returns HTTP 400 if invalid.

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": {
      "prompt": "<prompt>"
    },
    "name": "search_gemini_grounded_web"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesFactual question or search query to ground against live Google Search results.
recency_biasNoTemporal preference for search snippets; defaults to 'any_time' when omitted.

Output Schema

NameRequiredDescriptionDefault
modelYesGemini model used for grounded synthesis.
outputYesGrounded factual answer text.
citationsYesStructured Google Search grounding chunks and source URLs.
groundingYesGrounding source ('google_search').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover safety/idempotency, and the description goes well beyond them: statelessness, 32 KB payload cap, 60 RPM throttle, L402 pricing (75 sats) with a ?demo=true bypass, and HTTP 400 on invalid input. It loses a point because it asserts recency_bias 'defaults to past_24h', which conflicts with the schema and could mislead; the low-latency claim is also unquantified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then usage, then constraints - a sensible ordering with no filler sentences. The final sentence is an overloaded run-on packing limits, auth, defaults, and error codes into one clause chain, which slightly hurts scanability.

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?

For a two-param tool with a full output schema, this covers the operational essentials an agent needs: cost model, rate/payload ceilings, auth options, and failure mode. The only meaningful gap is the incorrect default it reports for the optional enum parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3 and the schema already documents both parameters. The description's only added parameter claim is that recency_bias defaults to 'past_24h', which directly contradicts the schema's 'any_time' - misleading guidance is worse than silence.

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?

States a specific verb and resource ('Answers factual queries with live Google Search grounding') plus the concrete payload (sourced answers + grounding metadata). The final clause explicitly names the sibling it replaces for geo queries, so an agent can discriminate without opening any 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?

'Use when verifying live web facts, documentation updates, or current events' gives positive selection criteria, and 'for querying geographic places, coordinates, directions, and local business data... use search_gemini_grounded_maps instead' names the alternative and the condition that routes to it.

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

Deploy Server

Other Tools