Skip to main content
Glama

NS Pros MCP Gateway

google-dev-knowledge__search_documents

Use this tool to find documentation about Google developer products. The documents contain official APIs, code snippets, release notes, best practices, guides, debugging info, and more. It covers the following products and domains:

  • ADK: adk.dev

  • Android: developer.android.com

  • Apigee: docs.apigee.com

  • Chrome: developer.chrome.com

  • Dart: dart.dev

  • Firebase: firebase.google.com

  • Flutter: docs.flutter.dev

  • Fuchsia: fuchsia.dev

  • Gemini CLI: geminicli.com

  • Genkit: genkit.dev

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-dev-knowledge__search_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. The raw query string provided by the user, such as "How to create a Cloud Storage bucket?".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It characterizes the corpus contents (APIs, code snippets, release notes, best practices) but says nothing about result count, ranking, freshness, snippet size, or whether results are paginated or full text.

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 purpose is front-loaded and the product list is genuinely useful scoping information. The list is long, ends with a dangling empty bullet, and appears truncated, which makes the definition look unfinished.

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

Completeness3/5

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

For a one-parameter read-only search with no output schema, the corpus scope is adequately conveyed. What an agent still cannot infer is how results come back and how this tool relates to sibling retrieval tools over the same documents.

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 at 100% schema coverage, and the schema already describes it as the raw user query with a worked example. The description adds no further guidance on query phrasing, length, or whether natural-language questions are preferred over keywords.

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?

States a specific verb and resource ("find documentation about Google developer products") and scopes the corpus with an explicit product/domain list (ADK, Android, Firebase, Flutter, etc.). It does not distinguish itself from likely siblings such as get_documents or answer_query, which appear to operate over the same corpus.

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?

"Use this tool to find documentation..." gives an implied trigger, and the domain list lets an agent judge topical relevance. There is no explicit when-not guidance and no named alternative for retrieving full documents or getting a synthesized answer, both of which appear to exist as siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.