Reveals all curated Google Workspace tools at once for substantial work, avoiding per-service discovery. Use before google_api_call to access Gmail, Drive, Calendar, Sheets, and Docs.
Reveal ALL curated Google tools at once (instead of per-service discovery). Use when starting substantial Google work; prefer these over google_api_call. Pair with discover_reset.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v5.4.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, so the safety profile is covered. The description adds real behavioral context beyond that: this bulk-reveals the curated toolset rather than a single service, and it should be paired with discover_reset, implying a persistent discovery state. It does not explain whether already-discovered tools are duplicated, but the gap is minor given annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences; the action and bulk scope are front-loaded, followed by usage conditions. No filler or restated title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters, no output schema, and annotations covering the safety profile, the description carries everything an agent needs: what is revealed, when to prefer it, and the companion reset tool. Nothing material is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so parameter semantics are trivially satisfied and the baseline is 4. Nothing in the description is needed to clarify inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Reveal') and resource ('ALL curated Google tools'), with the scope ('at once, instead of per-service discovery') that separates it from the gmail_discover/drive_discover family. An agent can distinguish it from every sibling without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly prescribes when to use it ('when starting substantial Google work'), names the alternative it replaces (per-service discovery) and the downstream preference over google_api_call, and pairs it with discover_reset. When-to-use, alternative, and follow-up are all present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.