@alvera-ai/platform-sdk 0.10.0-rc.13 → 0.10.0-rc.15

package/.agent/custom_datasets.md

@@ -66,7 +66,7 @@ name:  'alvera_custom_contact_us_submissions'
 
 The `name` is what every downstream resource references —
 `.get(name)`, `generic_table_id` foreign keys via the resolved
-row, `datasets.metadata(tenantSlug, datalakeSlug, 'generic_table', { genericTableId })`,
+row, `datasets.metadataDetails(tenantSlug, datalakeSlug, 'generic_table', { genericTableId })`,
 etc. Never pre-compute `name` client-side; read it back from
 the create response. A server-side slugifier change would flip
 every downstream binding, so specs assert the derived `name`
@@ -278,10 +278,10 @@ poll above.
                                                tables expose `name`)
 ```
 
-Plus the polymorphic dataset surface for catalog markdown:
+Plus the polymorphic dataset surface for per-table markdown:
 
 ```typescript
-const { data: md } = await api.datasets.metadata(
+const { data: md } = await api.datasets.metadataDetails(
   tenantSlug,
   datalakeSlug,
   'generic_table',
@@ -290,6 +290,11 @@ const { data: md } = await api.datasets.metadata(
 // md: string — agent-facing markdown describing the table's schema
 ```
 
+For the whole-domain catalog (every system + custom dataset type
+registered to this datalake) use the sibling
+`api.datasets.metadata(tenantSlug, datalakeSlug)` — same shape as
+`tools.metadata` / `dataSources.metadata`.
+
 See `datalakes.md` §5 `.systemDatasets` for the system-dataset
 sibling of this verb; the `'generic_table'` kind is the entry
 point for custom-dataset metadata.

package/.agent/datalakes.md

@@ -567,8 +567,9 @@ operator-defined generic tables** — those live under
 `api.genericTables.list(...)`. The
 literal placeholder `"generic_table"` is also absent. Each name
 can be drilled into via
-`api.datasets.metadata(tenantSlug, datalakeSlug, name)` for
-agent-facing markdown. Pair `.systemDatasets()` with a
+`api.datasets.metadataDetails(tenantSlug, datalakeSlug, name)` for
+agent-facing markdown, or the whole-domain catalog can be fetched
+in one shot via `api.datasets.metadata(tenantSlug, datalakeSlug)`. Pair `.systemDatasets()` with a
 `page_size: 1` probe per name as a post-migration smoke (proves
 each industry-built table is queryable; the post-ready probe
 code is in §6 Gotcha 3).
@@ -581,7 +582,7 @@ const { data: catalog } = await api.datalakes.systemDatasets(
 // catalog.datasets: sorted, unique array of industry-built dataset names
 
 for (const name of catalog.datasets) {
-  const { data: md } = await api.datasets.metadata(tenantSlug, datalakeSlug, name)
+  const { data: md } = await api.datasets.metadataDetails(tenantSlug, datalakeSlug, name)
   // md is a string — agent-facing markdown describing the dataset
 }
 ```

package/.agent/tool-call-configs.md

@@ -0,0 +1,90 @@
+<!-- alvera:doc kind="tool-call-configs" generated-by="mix alvera.dump.static_metadata" -->
+
+# Tool Call Configurations
+
+Per-invocation invocation-side schemas for Alvera tools. Each section
+documents one variant of `Platform.Tools.ToolCallConfig`, identified
+by its atom and rendered by `ToolCallConfig.metadata_details/2`.
+
+<!-- alvera:section kind="tool-call-config" atom="restapi_request" module="Platform.Tools.ToolCallConfig.RESTAPIRequest" -->
+
+## Tool Call Configuration (restapi_request)
+
+Fetches data via REST API with pagination support.
+
+- **method** (enum: head, get, put, post, delete, patch) — HTTP method
+- **path** (TemplateConfig) — API endpoint path, rendered as Liquid template
+- **body** (TemplateConfig, nullable) — Request body, rendered as Liquid template
+- **params** (TemplateConfig, nullable) — Query parameters, rendered as Liquid template
+- **pagination_context_template** (TemplateConfig) — Pagination control template, must render to JSON with `has_next` boolean field
+
+<!-- alvera:section kind="tool-call-config" atom="sql_query" module="Platform.Tools.ToolCallConfig.SQLQuery" -->
+
+## Tool Call Configuration (sql_query)
+
+Fetches data via SQL query with Liquid template variables for pagination.
+
+- **query** (TemplateConfig) — SQL query template with pagination variables
+
+<!-- alvera:section kind="tool-call-config" atom="sftp_request" module="Platform.Tools.ToolCallConfig.SFTPRequest" -->
+
+## Tool Call Configuration (sftp_request)
+
+Fetches data from a remote SFTP server.
+
+- **path** (string) — Remote file path on SFTP server
+- **content_type** (string) — MIME type of the file
+
+<!-- alvera:section kind="tool-call-config" atom="microsoft_share_point_excel_request" module="Platform.Tools.ToolCallConfig.MicrosoftSharePointExcelRequest" -->
+
+## Tool Call Configuration (microsoft_share_point_excel_request)
+
+Fetches data from a Microsoft SharePoint drive (Excel files).
+
+- **drive_url** (string) — SharePoint drive URL
+- **azure_tenant_id** (string) — Microsoft Azure tenant identifier
+- **sheet_number** (integer) — 0-indexed Excel sheet number
+- **search_params** (string) — Search parameters for locating files
+
+<!-- alvera:section kind="tool-call-config" atom="aws_lambda_request" module="Platform.Tools.ToolCallConfig.AWSLambdaRequest" -->
+
+## Tool Call Configuration (aws_lambda_request)
+
+Invokes an AWS Lambda function to fetch data.
+
+- **payload** (TemplateConfig) — Lambda JSON payload, rendered as Liquid template
+- **timeout_ms** (integer, default: 600000, max: 900000) — Invocation timeout in milliseconds
+
+<!-- alvera:section kind="tool-call-config" atom="s3_request" module="Platform.Tools.ToolCallConfig.S3Request" -->
+
+## Tool Call Configuration (s3_request)
+
+Fetches data from an S3 bucket.
+
+- **file_path** (string) — S3 object key (no `s3://` prefix)
+
+<!-- alvera:section kind="tool-call-config" atom="manual_upload" module="Platform.Tools.ToolCallConfig.ManualUpload" -->
+
+## Tool Call Configuration (manual_upload)
+
+Manual file upload — data is uploaded directly by the user. No additional configuration fields.
+
+<!-- alvera:section kind="tool-call-config" atom="sms_request" module="Platform.Tools.ToolCallConfig.SMSRequest" -->
+
+## Tool Call Configuration (sms_request)
+
+Sends an SMS message via the configured SMS provider.
+
+- **to** (TemplateConfig) — Recipient phone number in E.164 format, rendered as Liquid template
+- **body** (TemplateConfig) — Message body, rendered as Liquid template
+- **sms_type** (enum: transactional, promotional) — Message classification; defaults to `transactional`
+
+<!-- alvera:section kind="tool-call-config" atom="email_request" module="Platform.Tools.ToolCallConfig.EmailRequest" -->
+
+## Tool Call Configuration (email_request)
+
+Sends an email message via the configured email provider.
+
+- **to** (TemplateConfig) — Recipient email address (RFC 5322), rendered as Liquid template
+- **subject** (TemplateConfig) — Email subject line, rendered as Liquid template
+- **body** (TemplateConfig) — Email body, rendered as Liquid template