Skip to main content
Glama

NS Pros MCP Gateway

google-dev-knowledge__get_documents

Use this tool to retrieve the full Markdown content of a single document or up to 20 documents in a single call by passing a list of document resource names in the names parameter (e.g., get_documents(names=["documents/..."]); the parameter is names taking a list of strings, not name). Always obtain exact documents/{uri_without_scheme} resource names from the parent field of search_documents results or the references field of answer_query results first; never guess or construct

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": {
      "names": "<names>"
    },
    "name": "google-dev-knowledge__get_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesRequired. List of 1 to 20 document resource names (`names`) to retrieve in a single call (for either a single document or multiple documents), exactly as returned by the `parent` field of `search_documents` results or the `references` field of `answer_query`. Do not pass a single string or use a `name` parameter, and never guess or construct `documents/...` paths without calling `search_documents` or `answer_query` first. The documents are returned in the same order as the `names` in the request. Format: `documents/{uri_without_scheme}` Example: `documents/docs.cloud.google.com/storage/docs/creating-buckets`

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the essentials: this is a read of full Markdown content, batch-capped at 20, results returned in request order. It stops short of stating failure behavior for invalid/unknown names or any truncation/size limits on returned content.

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?

Front-loaded with the purpose, which is good, but it is a single run-on sentence with heavy nested parentheses and it ends abruptly at 'never guess or construct' as if truncated. Substantial content is duplicated with the input schema, so it is denser and more repetitive than needed.

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

Completeness5/5

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

For a one-parameter retrieval tool with no output schema, the description covers the name-sourcing requirement, the format, the batch cap, and the return shape (full Markdown, same order). An agent has everything needed to invoke it correctly.

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% and the schema already documents the 1-20 list, the `documents/{uri_without_scheme}` format, the example, and the 'not `name`' warning, so the description largely restates it. The reinforcement of the naming pitfall is helpful but adds little genuinely new semantic content beyond the schema.

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 ('retrieve the full Markdown content of a single document or up to 20 documents in a single call') and pins down the exact mechanism (`names` list). The batching scope and the pointer to sibling tools make it unmistakable versus search_documents or answer_query.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite workflow: get exact `documents/{uri_without_scheme}` names from the `parent` field of `search_documents` results or the `references` field of `answer_query` first, and never guess or construct paths. That is a clear when-to-use plus a named alternative for the lookup step.

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.