Skip to main content
Glama

Google_drive

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

TDQS

A4.8/5.0
Behavior5/5

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

Annotations indicate read-only, open-world, idempotent, non-destructive behavior. The description adds details about fan-out to multiple sources, fallback logic, and soft-fail for USPTO. No contradictions.

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?

The description is front-loaded with examples and purpose. It is informative but somewhat dense; a bulleted list could improve readability, but it remains efficient without unnecessary words.

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?

The description covers core functionality, sources, input format, and output structure. It could mention potential limitations like pagination or rate limits, but annotations suffice for safety. Overall adequate.

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

Parameters5/5

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

Schema coverage is 100%. The description adds meaning by explaining 'since' accepts ISO dates or relative shorthand, and 'value' can be ticker or CIK. This aids correct parameter use.

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?

The description clearly states the tool's purpose as a change feed for a company, with concrete examples of queries it answers. It distinguishes from the sibling tool entity_profile by specifying when to use each.

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?

The description explicitly provides use cases and contrasts with entity_profile for static profiles. It also gives guidance on the 'since' parameter format and typical values like '30d'.

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

All Google_drive toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Many tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer queries, and the multiple polymarket_* tools scan for edges and arbitrage. The Drive tools are distinct, but the surrounding 31 unrelated tools create significant ambiguity about which tool to call for a given task.

Naming Consistency2/5

Tool names are all snake_case, but the pattern is inconsistent: some start with verbs (drive_create_file, ask_pipeworx, validate_claim), some are noun phrases (entity_profile, recent_changes, polymarket_edges), and some are bare verbs (remember, forget, recall). There is no uniform verb_noun convention, and suffixes like _beta and _grounded add further irregularity.

Tool Count1/5

36 tools is far too many for a server named Google_drive, especially since only 5 tools (drive_create_file, drive_get_content, drive_get_file, drive_list_files, drive_search) actually relate to Drive. The other 31 tools cover unrelated domains like Pipeworx data queries, Polymarket betting, and memory management, making the tool count wildly disproportionate to the server's apparent purpose.

Completeness2/5

For a Google Drive server, the tool set is incomplete: it covers create, get content, get metadata, list, and search, but lacks essential operations like updating, deleting, uploading, moving, copying files, creating folders, or managing permissions/sharing. These gaps would force agents to work around missing core Drive functionality.

Resources