Google Workspace MCP

workspace_schema

Read-only

Look up the exact request parameters for any Google Workspace API method before making calls. Avoid guesswork by reading schema from Google's discovery service.

Instructions

The exact parameters and request body a method expects, straight from Google's discovery service. Read this before workspace_raw rather than guessing field names.

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": {
      "method": "<method>"
    },
    "name": "workspace_schema"
  }
}

Input Schema

Name	Required	Description	Default
`method`	Yes	Dotted, e.g. "drive.files.list" or "gmail.users.messages.send"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds behavioral context beyond those: the data comes straight from Google's discovery service, and it is meant to inform calls to workspace_raw rather than being executed itself.

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?

Two short sentences front-load the core value proposition and then give concrete usage direction. Every sentence earns its place with no filler or repetition.

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?

For a simple one-parameter introspection tool with readOnlyHint and openWorldHint, the description is sufficient: it states what is returned and how to use it before workspace_raw. A small gap is that it doesn't describe the response structure, but the discovery-service framing covers most of what an agent needs.

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 description coverage is 100%, and the schema already documents the 'method' parameter with dotted examples. The description adds context about the parameter's purpose, but it does not add new semantic detail beyond what the input schema already provides, so the baseline of 3 is appropriate.

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?

The description clearly identifies the tool as a schema/metadata lookup: it returns 'the exact parameters and request body a method expects' from Google's discovery service. It distinguishes itself from sibling workspace_raw by positioning itself as the read-before-execute step, so an agent can tell them apart.

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?

It explicitly tells the agent when to use it: 'Read this before workspace_raw rather than guessing field names.' This names the relevant sibling and gives clear temporal ordering, leaving no ambiguity about when this tool is appropriate.

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