FastMCP Google Docs Manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_documentsB | List Google Docs files from your Google Drive. |
| read_documentB | Read the text content of a Google Doc by its document ID. |
| create_documentB | Create a new Google Doc with a title and body content. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: create_document for creation, list_documents for listing, and read_document for reading content. There is no overlap or ambiguity in their functions, making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern (create_document, list_documents, read_document) with no deviations. The naming is predictable and readable throughout the set.
With only 3 tools, the server feels thin for a Google Docs manager, as it lacks update and delete operations. While the tools cover basic CRUD aspects (create, list, read), the count is borderline low for the apparent scope of document management.
The tool set covers create, list, and read operations, but there are notable gaps such as update_document and delete_document for full lifecycle management. Agents can work around this for basic tasks, but the surface is incomplete for comprehensive document handling.