Skip to main content
Glama
dipseth

google-workspace-unlimited

Tool Enable/Disable Management

manage_tools
Destructive

List, enable, or disable FastMCP tools at runtime, globally or per session. Use service_filter to target all tools for a service like gmail or drive.

Instructions

List, enable, or disable FastMCP tools at runtime. Supports both global scope (affects all clients) and session scope (affects only current session). Use service_filter to target all tools for a service (e.g., 'gmail', 'chat', 'drive') without needing to know individual tool names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoScope of the operation: 'global' (default) - affects all MCP clients connected to this server, 'session' - affects only the current client session (other clients unaffected). Session scope requires SessionToolFilteringMiddleware to be enabled.global
actionYesAction to perform: 'list' (show all tools), 'disable' (disable specific tools), 'enable' (enable specific tools), 'disable_all_except' (disable every tool except a kept list and protected infra tools), 'enable_all' (enable all tools in the registry).
tool_namesNoTool name(s) to enable/disable. Single string ('tool_a'), list (['tool_a', 'tool_b']), comma-separated ('tool_a,tool_b'), or JSON ('["tool_a","tool_b"]'). Required for enable/disable actions.
service_filterNoFilter tools by service name (e.g., 'gmail', 'chat', 'drive'). When provided, automatically resolves matching tool names from the registry using extract_service_from_tool(). Can be used instead of tool_names.
include_internalNoIf True, include internal/system tools (names starting with '_') in listing
user_google_emailNoUse 'me' or 'myself' for auto-resolution to authenticated user, or provide specific email address. If None, uses current authenticated user (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if the overall operation failed
scopeNoScope of the operation: 'global' affects all clients, 'session' affects only the current sessionglobal
actionYesAction performed: 'list', 'enable', 'disable', 'disable_all_except', or 'enable_all'
errorsNoList of error messages for individual tool operations that failed
messageYesHuman-readable summary of the operation
successYesWhether the tool management operation succeeded
toolListNoFull list of tools with their status (for 'list' action)
totalToolsYesTotal number of tools in the registry
enabledCountYesNumber of currently enabled tools (global state)
sessionStateNoSession-specific tool state (included when scope='session' or action='list')
toolsSkippedNoList of tool names that were skipped (protected or not found)
disabledCountYesNumber of currently disabled tools (global state)
toolsAffectedNoList of tool names that were enabled/disabled by this operation
protectedToolsYesList of tool names that are protected from being disabled
clientSupportsUINoWhether the connected client supports the MCP Apps UI extension
enabledToolNamesNoList of tool names currently enabled for this session. Returned after modify actions (enable/disable) to allow clients to update their tool list without requiring a separate list_tools call or notification handling.
Behavior4/5

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

Annotations already indicate destructiveHint=true. The description adds context about scope affecting all clients vs. current session, and mentions that session scope requires middleware. It also explains that service_filter automatically resolves tool names. These details go beyond the annotations.

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?

The description is extremely concise: two sentences that cover purpose and a key usage tip. No extraneous words, and the most important information is front-loaded.

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?

Given the tool has 6 parameters and an output schema, the description covers the essential behavioral aspects (runtime management, scope, service filter). It is sufficient for an agent to understand the tool's role, though it could briefly mention that disabling tools affects availability.

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%, so the schema already documents all parameters thoroughly. The description merely summarizes the key points (scope, service_filter) without adding new semantic information beyond what's in the schema.

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 states the tool lists, enables, or disables FastMCP tools at runtime. It specifies support for global and session scopes and mentions the service_filter for targeting all tools of a service. This is distinct from all sibling tools which are specific Google Workspace operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear use case for the service_filter parameter ('without needing to know individual tool names'), implying when to use this parameter over tool_names. It does not explicitly state when not to use the tool or list alternatives, but given the sibling tools are all different, this tool's purpose is self-evident.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dipseth/google_workspace_fastmcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server