Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

drive_menu

Lists the actions available in Google Drive's 'More actions' menu for a specified item without executing any, helping you inspect options before choosing.

Instructions

List the actions Drive offers for an item (its 'More actions' menu), without running any.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "drive_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoExact item name in the current location.
pathNoFolder holding the item ("/A/B" from My Drive, "A/B" relative); default: the location of the last listing.
indexNoIndex from the last drive.list / drive.search.
occurrenceNoWhich item when several share the name (0 = first).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that no action is run, implying a safe read-only inspection, but it does not explain permissions, item-resolution behavior, or what the returned action list looks like.

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?

It is a single, front-loaded sentence with no wasted wording. The key distinction from execution tools is stated immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and its parameters are fully documented in the schema, but there is no output schema and the description does not describe the return format. For a menu-listing tool, that leaves a modest but real gap around what the agent will receive.

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 all four optional parameters are already documented in the schema. The description adds no additional parameter semantics, making the baseline score of 3 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 states a specific verb and resource: listing Drive actions for an item. The parenthetical 'More actions' menu and the phrase 'without running any' make clear this is a discovery tool rather than an action-executing sibling like drive_open or drive_share.

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 gives clear context for use: inspect the available actions on an item without executing them. It does not explicitly name alternative sibling tools or state when-not-to-use conditions, which keeps it below a 5.

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

Deploy Server

Other Tools