Skip to main content
Glama

Drive Connector

drive_connector
Read-onlyIdempotent

File storage across Google Drive, OneDrive, and Dropbox: list, search, and read user-uploaded documents, spreadsheets, PDFs, and other files. ONLY use this when the user explicitly asks about FILES, DOCUMENTS, or DRIVE contents (e.g. 'find my Q3 contract', 'list files in /Reports'). Do NOT use this to hunt for cached JSON or reports that might contain answers about other services (Shopify, GunBroker, QuickBooks, etc.) — call the corresponding service connector directly instead. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYessearch_drive: Search Google Drive files that the authenticated user has access to | list_drive_files: List files from Google Drive with pagination | search_my_onedrive: Search OneDrive files by name or content. Requires Microsoft authentication | search_my_dropbox: Search for files in Dropbox by name or content | read_sheet: Read data from a Google Sheets spreadsheet | get_drive_stats: Get statistics about the user's Google Drive including storage usage. Useful before iterating through a large drive | get_file_content: Get the content of a Google Drive file | get_my_onedrive_storage: Get OneDrive storage information including quota, used space, and remaining space. Use when user asks about 'my OneDrive | list_my_onedrive_files: List files from Microsoft OneDrive with pagination. Use when user asks 'show my OneDrive files'. Requires Microsoft auth | read_my_onedrive_file: Read the content of a file from OneDrive. Supports Word, Excel, PowerPoint, PDFs, and text files. Requires Microsoft aut | get_my_onedrive_recent: Get recently accessed files from OneDrive. Requires Microsoft authentication via /oauth/microsoft/authorize | get_my_onedrive_shared: Get files shared with the user in OneDrive. Requires Microsoft authentication via /oauth/microsoft/authorize | get_my_dropbox_storage: Get Dropbox storage information including quota, used space, and remaining space. Use when user asks about 'my Dropbox s | list_my_dropbox_files: List files in Dropbox. Supports pagination and filtering by folder. Use when user asks 'show my Dropbox files', 'what's | read_my_dropbox_file: Read content of a file from Dropbox. Supports Word docs, Excel, PowerPoint, PDFs, and text files | get_my_dropbox_recent: Get recently modified files from Dropbox | get_my_dropbox_account: Get information about the connected Dropbox account
paramsNoAction-specific parameters. search_drive: {query: string, max_results?: integer} | list_drive_files: {max_results?: integer, mime_type?: string, folder_id?: string} | search_my_onedrive: {query: string, max_results?: integer} | search_my_dropbox: {query: string, max_results?: integer} | read_sheet: {spreadsheet_id: string, range: string} | get_drive_stats: none | get_file_content: {file_id: string, page_start?: integer, page_end?: integer, search_term?: string} | get_my_onedrive_storage: none | list_my_onedrive_files: {folder_path?: string, max_results?: integer, page_token?: string} | read_my_onedrive_file: {file_id: string, page_start?: integer, page_end?: integer, search_term?: string} | get_my_onedrive_recent: {max_results?: integer} | get_my_onedrive_shared: {max_results?: integer} | get_my_dropbox_storage: none | list_my_dropbox_files: {folder_path?: string, max_results?: integer, cursor?: string} | read_my_dropbox_file: {path_or_id: string, page_start?: integer, page_end?: integer, search_term?: string} | get_my_dropbox_recent: {max_results?: integer} | get_my_dropbox_account: none

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: a 15-minute, cross-replica provenance_token receipt that lets chart_render preserve verified provenance, and the consequence of lacking one (values labeled unverified_model_data). It does not cover return format or pagination, but the added verification semantics are substantive.

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

Conciseness3/5

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

The purpose and routing guidance are front-loaded and efficient, but the tail is padded with cross-cutting policy — the attribution-footer rendering rules and the generic 'Data accuracy contract' boilerplate about campaign budgets, ROAS, CPA, and 'waste' — that is not specific to a file-storage connector and dilutes the tool-specific signal.

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?

For a 17-action multiplexed connector, the description establishes scope, cross-service routing, and the chart_render verification handoff, while the schema carries per-action semantics. It is close to complete; only return-format/pagination expectations are absent, and those are less critical for a read-only listing tool.

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% — the action enum documents all 17 actions and the params field documents each action's argument shape. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States specific verbs and resources: 'list, search, and read user-uploaded documents, spreadsheets, PDFs' across Google Drive, OneDrive, and Dropbox. It explicitly separates itself from sibling service connectors (Shopify, GunBroker, QuickBooks), so an agent can route correctly without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit positive trigger ('ONLY use this when the user explicitly asks about FILES, DOCUMENTS, or DRIVE contents') with examples, plus an explicit negative case and named alternative ('call the corresponding service connector directly instead'). Nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources