gws-mcp
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 |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Report Google authentication status (never contains secret material). |
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 1 tool
Only one tool exists, so there is no possibility of ambiguity or confusion between tools.
With a single tool, naming is trivially consistent and follows a clear pattern (verb_noun: auth_status).
A single tool for checking authentication status is extremely limited for a server named 'gws-mcp' which implies Google Workspace functionality. While it may serve a narrow purpose, the count feels too small for a meaningful integration.
The server only offers an auth status check, which is severely incomplete for any realistic Google Workspace interaction. There are no tools for managing resources, performing actions, or accessing data, so agents would hit dead ends immediately.