Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

drive_view

Switch the current Google Drive file list between list and grid layouts to match your browsing preference.

Instructions

Switch the current Drive list between list and grid view.

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_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNolist or grid.list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 clearly frames the action as a display-only view switch on the current Drive list, but it does not state whether the mode persists, applies per user or session, or whether any underlying data changes. For a low-complexity UI toggle this is minimum viable but not rich behavioral context.

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 a single efficient sentence with zero waste. The action and target are front-loaded, making it easy to parse quickly.

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?

This is a simple one-parameter tool with a fully described enum and no output schema, so the description need not explain return values. It states the operation clearly enough for invocation, though it could note whether the setting is persisted or scoped to the current view session.

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 mode parameter and its list/grid enum are already fully documented in the schema. The description reinforces the two modes but adds no extra semantics such as default behavior or persistence beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'Switch the current Drive list' between 'list and grid view.' It is clear enough to distinguish this as a view-mode toggle rather than a file-listing or navigation tool. It does not explicitly contrast itself with siblings such as drive_list or drive_menu, so it falls short of a 5.

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

Usage Guidelines3/5

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

The phrase 'current Drive list' implies the tool is used when the user wants to change how the current Drive view is displayed. However, there is no explicit guidance about when to use this instead of alternatives, nor any exclusions. Usage is implied but not spelled out.

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