Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

drive_location

Retrieves the current Google Drive screen state, including screen kind, title, sort order, view mode, and remembered folder path.

Instructions

Where Drive is now: screen kind, title, sort order, view mode and remembered folder path.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it partially discharges it by enumerating the state fields returned and implying a passive state query. It never explicitly states the operation is read-only/side-effect-free, nor how fresh or scoped the snapshot is, which matters for a state-inspection tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact clause with the key information front-loaded ('Where Drive is now') followed by the concrete fields. No waste, though it is a fragment rather than a complete sentence and could have carried one more routing hint at no cost.

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?

With no output schema and no annotations, the description must explain both behavior and returns; it lists several return fields but not exhaustively (no indication of structure, extra fields, or interaction with drive_cd/drive_view). Adequate but with clear gaps for an agent deciding whether to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The listed return fields give useful orientation even though params add nothing.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that this reports the current Drive UI state and enumerates the reported fields (screen kind, title, sort order, view mode, folder path). However, it is a noun-phrase label rather than a verb+resource statement, and it never distinguishes itself from nearby siblings such as drive_info, drive_view, or drive_list, so an agent cannot tell exactly what this adds over those.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus drive_info, drive_view, drive_cd, or drive_list, and no preconditions or exclusions. The agent must infer usage context entirely from the name.

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