Skip to main content
Glama
Sign In
gemini-grounding

gemini-grounding

by epilande
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search with Grounding

search_with_grounding

Search for current information across general, coding, documentation, and troubleshooting topics. Receive verified answers with source citations.

Instructions

Search for current information using Gemini grounding

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

Input Schema

NameRequiredDescriptionDefault
queryYes
contextNo
focusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only says 'using Gemini grounding', which is vague about what sources are searched, how results are returned, or any side effects. The lack of detail understates the tool's behavior.

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

Conciseness3/5

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

The description is very short (one sentence) and front-loaded with the verb, which is good. However, it is too terse and omits essential details, so it is not appropriately sized for the complexity.

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

Completeness1/5

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

Given the tool has 3 parameters and no output schema or annotations, the description is severely incomplete. It does not explain return values, parameter usage, or any nuances, making it inadequate for proper invocation.

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

Parameters1/5

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

Schema description coverage is 0%, but the description provides no information about any of the three parameters (query, context, focus). The agent has no semantic understanding beyond the parameter names and types, which is insufficient.

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 verb 'search' and the resource 'current information', and differentiates from siblings like 'search_documentation' by mentioning 'Gemini grounding'. This makes the purpose specific and distinct.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings such as 'search_developer_resources' or 'search_reddit'. The description does not provide context for choosing this over alternatives, leaving the agent without decision support.

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