Save a new query or update an existing one in AssetDB. Use this to preserve useful SQL queries for future use and sharing. New queries are created as drafts by default - set is_draft=False to publish them. Creating a new query (query_id=None): - Provide at minimum: name and query (SQL text) - Optionally add description, tags for organization Updating existing query (provide query_id): - Only specify fields you want to change - Leave others as None/unset to keep current values Tags help organize queries by team, purpose, or data domain. Use descriptive names like "cost-analysis", "security", "daily-reports".

Essential guide for working with AssetDB - read this before writing SQL queries. AssetDB is Stacklet's massive cloud asset warehouse containing billions of records across resources, costs, tags, and relationships. This guide explains the schema, performance best practices, and common query patterns. ⚠️ Critical: Many tables are extremely large and require careful indexing and filtering to avoid timeouts. This guide shows you how to query safely and efficiently.

Execute ad-hoc SQL queries against AssetDB without saving them. For one-time analysis or testing SQL before saving. Returns full result data and download links in multiple formats.

Browse the complete library of Stacklet documentation files. Returns all available documentation including user guides, API references, tutorials, and troubleshooting resources. Each file has a path and descriptive title. Start with "index_llms.md" - it's specifically designed as an LLM-friendly overview of all documentation and provides the best entry point for understanding Stacklet's features and capabilities. The glossary is also extremely valuable in understanding the most important concepts and their relationships. Use docs_read() with any of the returned file paths to get the actual content.

Read Stacklet documentation files for detailed guidance and reference information. Provides access to the complete Stacklet knowledge base including setup guides, feature explanations, API documentation, best practices, and troubleshooting help. Recommended reading order: 1. Start with "index_llms.md" for the big picture overview 2. Follow links to specific topics you need 3. Check troubleshooting guides for common issues All documentation is written in Markdown format and regularly updated to reflect the latest Stacklet features and best practices.

Export large governance datasets to CSV for analysis and reporting. Perfect for exporting thousands of resources, policies, executions, or other governance data when GraphQL pagination would be too slow. The server handles all paging and generates a downloadable CSV file. Process: 1. Define columns mapping GraphQL fields to CSV columns 2. Optionally add filters via params 3. Export runs asynchronously - use timeout=0 to return immediately 4. Use platform_dataset_lookup() to check progress and get download URL

Guide for exporting large datasets from Stacklet Platform - use for big data analysis. When you need to export thousands of governance records (policies, resources, executions, etc.), the dataset export tools provide server-side CSV generation that's much more efficient than paging through GraphQL connections. This guide explains how to structure export requests, handle large datasets, and work with the async export process. Essential for data analysis workflows.

Monitor dataset export progress and retrieve download links. Use this to check on exports started with platform_dataset_export(). Returns current status, progress info, and download URL when complete. Export states: - Processing: Export is running (shows progress if available) - Complete: Ready for download (includes download_url and expiry time) - Failed: Export encountered an error Set timeout > 0 to wait for completion, or timeout=0 for immediate status check. Download URLs are temporary and expire after a few hours.

Get detailed GraphQL type definitions to understand schema structure. Returns the full GraphQL Schema Definition Language (SDL) for specified types, showing all fields, arguments, relationships, and documentation. Essential for building correct queries. Use this after platform_graphql_list_types() to understand: - What fields are available on each type - Required vs optional arguments - Relationships between types - Input types for mutations The SDL output shows exactly how to structure your GraphQL queries.

Essential guide for Stacklet Platform GraphQL API - read this first before using other tools. The Platform API provides access to all Stacklet governance features: policies, account groups, bindings, resources, executions, and more. This guide explains the GraphQL schema patterns, connection-based pagination, filtering, and best practices for effective queries. ⚠️ Always check this guide first - it contains critical information about schema introspection, filtering syntax, and performance considerations for large-scale governance data.

Discover available GraphQL types in the Stacklet Platform API. Use this to explore the schema and find the right types for your queries. Essential for understanding what data is available and how types relate to each other. Without a filter, returns all available types. With a regex filter, narrows down to matching type names (e.g., "Account.*" finds AccountGroup, AccountList, etc.). Next step: Use platform_graphql_get_types() to see detailed definitions for interesting types.

Execute GraphQL queries against the Stacklet Platform for governance operations. This is your main tool for querying policies, account groups, bindings, resources, executions, and all other governance data. Supports both queries and mutations. ⚠️ Important guidelines: - Always query for "problems" field alongside your data - Use small page sizes (5-10) for exploration, larger for known datasets - Check types with platform_graphql_get_types() first - For large exports, use platform_dataset_export() instead