Skip to main content
Glama

list_drive_workspace

Read-onlyIdempotent

Lists files in the workspace hub, optionally scoped to a folder, so agents can find stored documents before retrieval.

Instructions

List all files stored in the workspace hub.

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": "list_drive_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed-world scope, so the safety profile is fully covered. The description adds only the "all files" completeness claim and the workspace location, and says nothing about pagination, result ordering, or how an empty folder value behaves, which is the main remaining behavioral unknown for a listing 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?

One short sentence with the action front-loaded and no filler, which is appropriate for a simple list tool. It is terse to the point of omitting needed detail rather than being padded.

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?

For a simple, annotated, read-only tool with no output schema, only a modest description is needed. Still, the undefined folder parameter and the absence of any note on result scope or volume leave a gap an agent would want closed before relying on it.

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

Parameters2/5

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

The single optional parameter "folder" has 0% schema description coverage and the description never mentions it, so there is no explanation of what it filters, whether it accepts a path, or what the default empty string means. With low coverage the description was obligated to compensate and does not.

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 ("List all files") plus a location ("workspace hub"), which distinguishes it reasonably well from read_drive_file and write_drive_file. It falls short of 5 because "workspace hub" is not clearly related to the drive terminology used by its siblings, so an agent must infer the relationship.

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 explicit when-to-use guidance, no exclusions, and no reference to alternatives such as search_drive_rag for filtered lookup or read_drive_file for content retrieval. The word "all" vaguely implies unfiltered enumeration, but nothing tells the agent when this tool is the wrong choice.

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