Skip to main content
Glama
Sign In
gemini-grounding

gemini-grounding

by epilande
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Developer Resources

search_developer_resources

Search for developer resources and documentation to find relevant guides, APIs, and code examples based on query, language, or framework.

Instructions

Search specifically for developer resources and documentation

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

Input Schema

NameRequiredDescriptionDefault
queryYes
languageNo
frameworkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states 'search specifically', implying read-only behavior, but does not confirm safety (e.g., no mutations, no side effects). No additional traits are revealed.

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

Conciseness2/5

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

The description is only one sentence, which is too brief to be effective. While short, it omits critical details (parameter semantics, usage boundaries), making it under-specified rather than concise.

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 low schema coverage, lack of output schema, and missing annotations, the description is completely inadequate to guide correct invocation. It fails to explain parameters or distinguish from siblings, leaving the agent with minimal useful context.

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%, yet the description adds no information about the three parameters (query, language, framework). The agent must rely solely on parameter names, which are ambiguous (e.g., 'language' could mean programming language or human language).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches for developer resources and documentation, using a specific verb and domain. However, it does not differentiate from the sibling 'search_documentation', which likely overlaps in purpose.

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 is provided on when to use this tool versus alternatives. There are no explicit conditions, exclusions, or references to sibling tools, leaving the agent to infer usage context.

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