Skip to main content
Glama

docs get document

docs_get_document
Read-onlyIdempotent

Retrieve a Google Doc's title, headings, table count, and truncated plain-text body by document ID so agents can inspect document content without editing it.

Instructions

Read a Google Doc: title, headings, table count and plain-text body (truncated).

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": {
      "document_id": "<document_id>"
    },
    "name": "docs_get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_charsNo
document_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond them: the body comes back truncated. It does not say how truncation is signaled, what happens on a missing document, or how large documents behave, so the addition is real but thin.

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?

A single front-loaded sentence that names the resource first and the payload second, with zero filler. Nothing needs rewording or removing.

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

Completeness4/5

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

An output schema exists, so return shapes need not be described, and the safety profile is fully covered by annotations. What remains missing is small but non-trivial: the accepted format of document_id and the meaning/effect of max_chars.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters. The description alludes to truncation, which hints at max_chars, but never explains it (default 20000 is only in the schema) and says nothing about document_id format — whether a bare ID, a URL, or an ID from drive_search_files is expected. With zero schema coverage, the description needed to carry this and does not.

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 ('Read') and resource ('a Google Doc') and enumerates what comes back (title, headings, table count, plain-text body). This clearly separates it from the docs_create/append/insert/replace siblings without naming them, though it never explicitly distinguishes itself from drive_read_file, which could also retrieve document content.

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?

There is no when-to-use guidance, no prerequisites (e.g., whether the caller needs document access permission), and no exclusion of the obvious alternative drive_read_file or drive_download_file. The agent must infer from the returned-fields list that this is the structured-doc read path.

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