Skip to main content
Glama
gemini-search

gemini-search

by spotmaxtech

Google Search

google_search
Read-only

Searches the web via Google Search and Gemini grounding, returning a summarized answer with inline citations and source URLs for current facts or information outside training data.

Instructions

Searches the web with Google Search (via Gemini grounding) and returns a summarized answer with inline citations [n] and a list of source URLs. Use it for up-to-date information or facts not in your training data.

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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe search query or question to look up on the web.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing the output contract: a summarized answer with numbered inline citations plus a source URL list, which tells the agent the results are synthesized rather than raw links. It does not mention latency, cost, rate limits, or what an empty/no-result response looks like.

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 tight sentences: what it does and returns first, then the selection rule. Every clause carries information — no filler, no repetition of the title alone.

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?

A one-parameter, annotation-rich tool needs little more, and the description pre-empts the missing output schema by describing the return format. Remaining minor gaps are operational rather than semantic: no note on result volume, failure/empty behavior, or grounding-specific latency.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains the query field. The only added nuance is that the query may be phrased as a question, which the schema's own wording ("query or question") already conveys. Baseline 3 applies when the schema does the heavy lifting.

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 ("Searches the web with Google Search") and goes on to name both the return shape (summarized answer with inline citations [n]) and the supporting data (a list of source URLs). The parenthetical "via Gemini grounding" pins down the mechanism, so an agent knows exactly what it is invoking.

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?

Gives a concrete selection rule: "Use it for up-to-date information or facts not in your training data." That clearly tells the agent when this tool's knowledge is preferable to its own parametric memory. It stops short of explicit exclusions or alternatives (there are no sibling tools to route against), but no misleading implication is present.

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