Skip to main content
Glama
Sign In
orieg/gws-connector

orieg/gws-connector

by orieg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

gws.drive.list_folder

Read-only

List files and subfolders inside a Google Drive folder, returning IDs, names, MIME types, modified times, and sizes. Omit folderId to list the account's root directory.

Instructions

List the files and subfolders directly inside a Drive folder (non-recursive). Returns each item's file ID, name, MIME type, modified time, and size. Omit folderId to list the account's Drive root.

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": "gws.drive.list_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount label or email. Uses default if omitted.
folderIdNoFolder ID (default: root)
maxResultsNoMaximum files to return (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. Description adds meaningful behavioral details: non-recursive, returns specific fields, and root default. This exceeds the bare annotation coverage without contradicting it.

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?

Two sentences, front-loaded with the primary action, then return details and a usage tip. Efficient and well-structured with no redundant information.

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

Completeness5/5

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

For a simple list tool, the description plus schema and annotations provide a complete picture: what it does, what it returns, how to access root, and safety profile. No output schema is needed because the return fields are explicitly described.

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 coverage is 100%, so baseline is 3. The description adds slight value by explaining the root-default behavior of folderId, but this is already present in the schema ('default: root'). No significant extra meaning beyond 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?

Description clearly states the action (list) and the target resource (files/subfolders in a Drive folder), with specific scope (non-recursive). It distinguishes itself from sibling tools like gws.drive.search and gws.drive.read_file by the semantics of direct listing.

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?

Provides clear context on how to use the tool (omit folderId for root) but does not explicitly discuss when not to use it or recommend alternatives. The nature of the tool makes the intended use obvious, but explicit exclusions would strengthen it.

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