Gemini MCP Server

by salviz

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

gemini_search_grounded

Fetch up-to-date answers by sending a prompt with Google Search grounding and optional URL context to Gemini.

Instructions

Send a prompt to Gemini with Google Search grounding and URL context for up-to-date information

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": "gemini_search_grounded"
  }
}

Input Schema

Name	Required	Description
`model`	No	Model name (default: gemini-3.1-pro-preview)
`prompt`	Yes	The prompt to send with search grounding
`enableUrlContext`	No	Also enable URL context (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jun 29, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided, so the description must convey behavioral traits. It only states it sends a prompt with grounding but does not disclose whether it is read-only, destructive, requires authentication, or has rate limits. Very limited behavioral context.

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?

Single sentence, front-loaded with key action and context, no unnecessary words or fluff. Very concise and structured.

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

Completeness2/5

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

Given no output schema, the description does not explain what the response contains. Also lacks details on prerequisites, return format, or error handling. Incomplete for a tool that returns search results.

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 descriptions for each parameter. The description adds little beyond schema, implying defaults for model and enableUrlContext but not providing additional semantic meaning. Baseline score of 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 sends a prompt to Gemini with Google Search grounding and URL context, which is a specific verb-resource combination. It distinguishes from sibling tools like gemini_chat that lack explicit search grounding.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives, but the implication is clear from the name and description that it is for up-to-date information. Lacks explicit when-not-to-use or alternatives.

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