drive_unhide_shared_drive
Unhide a shared drive, restoring its visibility in the default view.
Instructions
Restore a shared drive to the default view
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| driveId | Yes | The ID of the shared drive to unhide |
Unhide a shared drive, restoring its visibility in the default view.
Restore a shared drive to the default view
| Name | Required | Description | Default |
|---|---|---|---|
| driveId | Yes | The ID of the shared drive to unhide |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. States it restores to default view, but does not disclose permissions, side effects, or reversibility. Bare minimum for a simple tool.
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?
Single sentence, 8 words, highly concise. Could add a bit more context without being verbose, but efficient.
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?
Sufficient for a simple tool with one parameter, but lacks mention of prerequisites, error states, or contrast with drive_hide_shared_drive. Could be more complete.
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?
Schema has 100% coverage with clear description for driveId. Description adds no extra meaning beyond schema. Baseline score maintained.
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?
Description uses specific verb 'restore' and resource 'shared drive', clearly indicating the inverse of hiding. Distinguishes from siblings like drive_hide_shared_drive, drive_delete_shared_drive.
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?
Implies usage after hiding a shared drive, but no explicit when-to-use, when-not-to-use, or alternatives given. No guidance on prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/salviz/google-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server