teardrop-cli 0.1.1__tar.gz → 0.3.0__tar.gz

{teardrop_cli-0.1.1 → teardrop_cli-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: teardrop-cli
-Version: 0.1.1
+Version: 0.3.0
 Summary: Command-line interface for the Teardrop AI agent platform
 Project-URL: Homepage, https://github.com/teardrop-ai/teardrop-cli
 Project-URL: Repository, https://github.com/teardrop-ai/teardrop-cli
@@ -45,7 +45,7 @@ Requires-Dist: httpx>=0.27
 Requires-Dist: keyring>=25.0
 Requires-Dist: platformdirs>=4.0
 Requires-Dist: rich>=13.0
-Requires-Dist: teardrop-sdk>=0.1.5
+Requires-Dist: teardrop-sdk>=0.2.0
 Requires-Dist: tomli-w>=1.0
 Requires-Dist: typer>=0.12
 Provides-Extra: dev
@@ -118,14 +118,19 @@ teardrop run "Summarize the latest ETH gas trends"
 | Goal | Command |
 |------|---------|
 | Create account & org | `teardrop auth signup` |
-| Sign in with wallet (existing key) | `teardrop auth login --siwe --key-file wallet.key` |
-| Generate a new wallet & sign in | `teardrop auth login --siwe --generate-wallet` |
+| Generate a new wallet & sign in | `teardrop auth login --siwe --generate-wallet [--save-key]` |
+| Sign in with wallet (existing key) | `teardrop auth login --siwe --key-file wallet.key [--save-key]` |
 | Email + password | `teardrop auth login --email you@example.com` |
 | Pre-issued JWT | `teardrop auth login --token <jwt>` |
+| Invite a team member | `teardrop auth invite colleague@example.com` |
 | Show identity | `teardrop auth status` |
 | Sign out | `teardrop auth logout` |
 
-Private keys are never persisted by the CLI. Sessions are stored in your OS keyring.
+Private keys are never persisted by the CLI unless you pass ``--save-key``.
+When saved, the key is stored in your OS keyring (never in a config file)
+and can be used for automatic re-authentication when the session token
+expires.  An encrypted keyring backend is required — plaintext fallbacks
+are refused.
 
 For machine-to-machine credentials, env-var precedence, and CI patterns, see [docs/cli-reference.md](docs/cli-reference.md#authentication).
 
@@ -181,6 +186,15 @@ teardrop run "Follow up" --thread <thread-id>
 # Pass structured context
 teardrop run "Process this order" --context '{"order_id":"ord_123"}'
 
+# Exclude specific tools
+teardrop run "Summarize news" --exclude platform/web_search
+
+# Estimate cost based on current pricing & config (no run performed)
+teardrop run "Analyze this data" --estimate-cost
+
+# Apply a tool policy from a file
+teardrop run "Execute workflow" --policy-file policy.json
+
 # Machine-readable output
 teardrop run "..." --json --no-stream
 
@@ -188,18 +202,76 @@ teardrop run "..." --json --no-stream
 teardrop run "..." --json --with-ui
 ```
 
-Streaming output renders Markdown live with inline tool calls. A token + cost summary prints at the end. By default, CLI output is optimized for scripting and automation (`emit_ui=false`); use `--with-ui` only if you need structured UI component data in the JSON output.
+Streaming output renders Markdown live with inline tool calls and structured UI components. A token + cost summary prints at the end. By default, CLI output is optimized for scripting and automation (`emit_ui=false`); use `--with-ui` only if you need structured UI component data in the JSON output.
+
+---
 
-If a run fails on credit, top up via the dashboard:
+## Automate Runs
+
+Use interval schedules for recurring prompts and event triggers for inbound webhooks:
 
 ```bash
-teardrop balance   # check credits
+teardrop schedules create \
+    --name hourly-briefing \
+    --prompt "Summarize open incidents" \
+    --interval-seconds 3600
+
+teardrop schedules list
+teardrop schedules runs <schedule-id>
+
+teardrop event-triggers create \
+    --name inbound-orders \
+    --prompt "Validate and process this order payload"
+
+teardrop event-triggers runs <trigger-id>
+teardrop event-triggers rotate-secret <trigger-id>
+```
+
+`event-triggers create` and `event-triggers rotate-secret` print the signing secret once. Store it immediately.
+
+Full reference: [docs/cli-reference.md](docs/cli-reference.md#schedules) and [docs/cli-reference.md](docs/cli-reference.md#event-triggers).
+
+---
+
+## Chat with an Agent
+
+A stateful chat mode that automatically continues the same thread across invocations:
+
+```bash
+teardrop chat "What is the current ETH gas price?"   # auto-creates a thread
+teardrop chat "Follow up on that"                     # continues the same thread
+teardrop chat "Start fresh" --new                     # starts a new conversation
+teardrop chat "Specific thread" --thread thr_abc123   # explicit thread by id
+teardrop chat "..." --json                            # machine-readable output
+```
+
+The active thread id is stored in `~/.teardrop/config.toml` and reused on your next `teardrop chat` call. The thread id is printed after every turn for copy/paste. All run flags (`--context`, `--exclude`, `--policy-file`, `--estimate-cost`, `--with-ui`, `--no-stream`) are supported.
+
+Use `teardrop run` for one-shot, script-friendly calls — use `teardrop chat` for conversational interaction.
+
+---
+
+If a run fails on credit, check your balance and history:
+
+```bash
+teardrop balance             # current credits
+teardrop balance credit-history   # past charges and top-ups
 ```
 
 To add credits, visit [teardrop.dev](https://teardrop.dev).
 
 ---
 
+## Agent Tools
+
+List all tools visible to your agent (platform, marketplace subscriptions, and your own tools):
+
+```bash
+teardrop agent-tools list
+```
+
+---
+
 ## Configure Your LLM
 
 One-shot bring-your-own-key wizard:

{teardrop_cli-0.1.1 → teardrop_cli-0.3.0}/README.md

@@ -58,14 +58,19 @@ teardrop run "Summarize the latest ETH gas trends"
 | Goal | Command |
 |------|---------|
 | Create account & org | `teardrop auth signup` |
-| Sign in with wallet (existing key) | `teardrop auth login --siwe --key-file wallet.key` |
-| Generate a new wallet & sign in | `teardrop auth login --siwe --generate-wallet` |
+| Generate a new wallet & sign in | `teardrop auth login --siwe --generate-wallet [--save-key]` |
+| Sign in with wallet (existing key) | `teardrop auth login --siwe --key-file wallet.key [--save-key]` |
 | Email + password | `teardrop auth login --email you@example.com` |
 | Pre-issued JWT | `teardrop auth login --token <jwt>` |
+| Invite a team member | `teardrop auth invite colleague@example.com` |
 | Show identity | `teardrop auth status` |
 | Sign out | `teardrop auth logout` |
 
-Private keys are never persisted by the CLI. Sessions are stored in your OS keyring.
+Private keys are never persisted by the CLI unless you pass ``--save-key``.
+When saved, the key is stored in your OS keyring (never in a config file)
+and can be used for automatic re-authentication when the session token
+expires.  An encrypted keyring backend is required — plaintext fallbacks
+are refused.
 
 For machine-to-machine credentials, env-var precedence, and CI patterns, see [docs/cli-reference.md](docs/cli-reference.md#authentication).
 
@@ -121,6 +126,15 @@ teardrop run "Follow up" --thread <thread-id>
 # Pass structured context
 teardrop run "Process this order" --context '{"order_id":"ord_123"}'
 
+# Exclude specific tools
+teardrop run "Summarize news" --exclude platform/web_search
+
+# Estimate cost based on current pricing & config (no run performed)
+teardrop run "Analyze this data" --estimate-cost
+
+# Apply a tool policy from a file
+teardrop run "Execute workflow" --policy-file policy.json
+
 # Machine-readable output
 teardrop run "..." --json --no-stream
 
@@ -128,18 +142,76 @@ teardrop run "..." --json --no-stream
 teardrop run "..." --json --with-ui
 ```
 
-Streaming output renders Markdown live with inline tool calls. A token + cost summary prints at the end. By default, CLI output is optimized for scripting and automation (`emit_ui=false`); use `--with-ui` only if you need structured UI component data in the JSON output.
+Streaming output renders Markdown live with inline tool calls and structured UI components. A token + cost summary prints at the end. By default, CLI output is optimized for scripting and automation (`emit_ui=false`); use `--with-ui` only if you need structured UI component data in the JSON output.
+
+---
 
-If a run fails on credit, top up via the dashboard:
+## Automate Runs
+
+Use interval schedules for recurring prompts and event triggers for inbound webhooks:
 
 ```bash
-teardrop balance   # check credits
+teardrop schedules create \
+    --name hourly-briefing \
+    --prompt "Summarize open incidents" \
+    --interval-seconds 3600
+
+teardrop schedules list
+teardrop schedules runs <schedule-id>
+
+teardrop event-triggers create \
+    --name inbound-orders \
+    --prompt "Validate and process this order payload"
+
+teardrop event-triggers runs <trigger-id>
+teardrop event-triggers rotate-secret <trigger-id>
+```
+
+`event-triggers create` and `event-triggers rotate-secret` print the signing secret once. Store it immediately.
+
+Full reference: [docs/cli-reference.md](docs/cli-reference.md#schedules) and [docs/cli-reference.md](docs/cli-reference.md#event-triggers).
+
+---
+
+## Chat with an Agent
+
+A stateful chat mode that automatically continues the same thread across invocations:
+
+```bash
+teardrop chat "What is the current ETH gas price?"   # auto-creates a thread
+teardrop chat "Follow up on that"                     # continues the same thread
+teardrop chat "Start fresh" --new                     # starts a new conversation
+teardrop chat "Specific thread" --thread thr_abc123   # explicit thread by id
+teardrop chat "..." --json                            # machine-readable output
+```
+
+The active thread id is stored in `~/.teardrop/config.toml` and reused on your next `teardrop chat` call. The thread id is printed after every turn for copy/paste. All run flags (`--context`, `--exclude`, `--policy-file`, `--estimate-cost`, `--with-ui`, `--no-stream`) are supported.
+
+Use `teardrop run` for one-shot, script-friendly calls — use `teardrop chat` for conversational interaction.
+
+---
+
+If a run fails on credit, check your balance and history:
+
+```bash
+teardrop balance             # current credits
+teardrop balance credit-history   # past charges and top-ups
 ```
 
 To add credits, visit [teardrop.dev](https://teardrop.dev).
 
 ---
 
+## Agent Tools
+
+List all tools visible to your agent (platform, marketplace subscriptions, and your own tools):
+
+```bash
+teardrop agent-tools list
+```
+
+---
+
 ## Configure Your LLM
 
 One-shot bring-your-own-key wizard:

teardrop_cli-0.3.0/docs/cli-json-schema.md

@@ -0,0 +1,130 @@
+# Teardrop CLI Agent Run JSON Schema
+
+When running `teardrop run "..." --json` or `teardrop chat "..." --json`,
+the output is a single JSON object (implies `--no-stream`).
+
+## Schema Details
+
+The JSON object contains the following fields:
+
+- `text` (string): The final text response from the agent.
+- `thread_id` (string | null): The ID of the thread used for the run. This can be used with the `--thread` flag in future runs (or `teardrop chat`) to continue the conversation.
+
+## Example Output
+
+```json
+{
+  "text": "The price of ETH is currently $2,450.32.",
+  "thread_id": "thr_abc123"
+}
+```
+
+## Usage
+To capture specific fields, use `jq`:
+```bash
+teardrop run "ETH price" --json | jq -r .text
+teardrop chat "ETH price" --json | jq -r .thread_id
+```
+
+---
+
+## Schedules (`schedules create/get/list/update --json`)
+
+`schedules list --json` returns a JSON array; all other commands return a single object.
+
+| Field | Type | Description |
+|---|---|---|
+| `id` | string (UUID) | Schedule identifier |
+| `org_id` | string | Owning org |
+| `user_id` | string | Creator user |
+| `name` | string | Display name |
+| `prompt` | string | Agent prompt |
+| `schedule_kind` | `"interval"` | Fixed constant |
+| `interval_seconds` | integer | Run frequency |
+| `enabled` | boolean | Active state |
+| `callback_url` | string \| null | Webhook called after each run |
+| `next_run_at` | string (ISO 8601) | Next scheduled time |
+| `last_run_at` | string \| null (ISO 8601) | Last completed run |
+| `consecutive_failures` | integer | Failures since last success |
+| `created_at` | string (ISO 8601) | |
+| `updated_at` | string (ISO 8601) | |
+
+```bash
+teardrop schedules create --name my-schedule --prompt "..." --interval-seconds 3600 --json | jq -r .id
+teardrop schedules update <id> --enabled false --json | jq .enabled
+teardrop schedules list --json | jq '.[].name'
+```
+
+---
+
+## Event Triggers (`event-triggers create/get/list/update --json`)
+
+`event-triggers list --json` returns a JSON array; all other commands return a single object.
+
+| Field | Type | Description |
+|---|---|---|
+| `id` | string (UUID) | Trigger identifier |
+| `org_id` | string | Owning org |
+| `user_id` | string | Creator user |
+| `name` | string | Display name |
+| `prompt` | string | Prompt template (supports `{{field}}` / `{{event_json}}`) |
+| `schedule_kind` | `"event"` | Fixed constant |
+| `enabled` | boolean | Active state |
+| `callback_url` | string \| null | Webhook called after each run |
+| `trigger_token` | string | Public route discriminator |
+| `event_path` | string | Inbound dispatch path (e.g. `/agent/events/{trigger_token}`) |
+| `consecutive_failures` | integer | Failures since last success |
+| `last_run_at` | string \| null (ISO 8601) | |
+| `created_at` | string (ISO 8601) | |
+| `updated_at` | string (ISO 8601) | |
+
+**`event-triggers create --json` only** additionally includes:
+
+| Field | Type | Description |
+|---|---|---|
+| `secret` | string | Plaintext signing secret — shown once, never retrievable again |
+
+**`event-triggers rotate-secret --json`** returns the rotation model (not the full trigger object):
+
+| Field | Type | Description |
+|---|---|---|
+| `id` | string (UUID) | Trigger identifier |
+| `secret` | string | New plaintext signing secret — shown once |
+
+```bash
+# Capture id and secret on creation for use in CI
+eval $(teardrop event-triggers create --name ci-hook --prompt "..." --json \
+  | jq -r '"TRIGGER_ID=" + .id, "TRIGGER_SECRET=" + .secret')
+
+teardrop event-triggers list --json | jq '.[].trigger_token'
+teardrop event-triggers rotate-secret <id> --json | jq -r .secret
+```
+
+---
+
+## Run History (`schedules runs / event-triggers runs --json`)
+
+Both commands return the same paginated envelope:
+
+```json
+{ "items": [ <ScheduledRunResult>, ... ], "next_cursor": "<cursor> | null" }
+```
+
+Each `ScheduledRunResult` item:
+
+| Field | Type | Description |
+|---|---|---|
+| `id` | string (UUID) | Outcome record ID |
+| `schedule_id` | string (UUID) | Owning schedule or trigger ID |
+| `org_id` | string | |
+| `run_id` | string (UUID) | Core execution thread ID |
+| `status` | `"completed" \| "failed" \| "timeout" \| "skipped"` | |
+| `output_text` | string | Synthesized agent output |
+| `cost_usdc` | integer | Atomic USDC charged ($1.00 = `1000000`) |
+| `error` | string | Sanitized reason on failure; empty on success |
+| `created_at` | string (ISO 8601) | |
+
+```bash
+teardrop schedules runs <id> --json | jq '.items[] | select(.status == "failed") | .error'
+teardrop event-triggers runs <id> --limit 50 --json | jq '.next_cursor'
+```

{teardrop_cli-0.1.1 → teardrop_cli-0.3.0}/docs/cli-reference.md

@@ -8,6 +8,9 @@ This document covers every flag, env var, and subcommand. For the quick path, st
 
 - [Authentication](#authentication)
 - [Running Agents](#running-agents)
+- [Chat Sessions](#chat-sessions)
+- [Schedules](#schedules)
+- [Event Triggers](#event-triggers)
 - [Billing & Credits](#billing--credits)
 - [Tool Management](#tool-management)
 - [Marketplace](#marketplace)
@@ -90,6 +93,88 @@ Streaming output renders Markdown live with inline tool calls. A token + cost su
 
 ---
 
+## Chat Sessions
+
+```bash
+teardrop chat "What is the current ETH gas price?"   # auto-creates a thread
+teardrop chat "Follow up on that"                     # continues the same thread
+teardrop chat "Start fresh" --new                     # starts a new conversation
+teardrop chat "Specific thread" --thread thr_abc123   # explicit thread by id
+teardrop chat "..." --json                            # machine-readable output
+```
+
+The active thread id is stored in `~/.teardrop/config.toml` (`chat.active_thread_id`).
+The file is chmod'd 600 and the thread id is printed to stderr after every turn.
+
+**Flag precedence** (highest first):
+1. `--new` — clears the stored thread; a fresh one is created server-side.
+2. `--thread <id>` — overrides any stored thread.
+3. **Stored thread** — read from config if neither `--new` nor `--thread` is given.
+4. **Server‑minted** — if none of the above resolve to a value, the server assigns one and it is persisted automatically.
+
+Chat supports all the same options as `run` (`--context`, `--exclude`, `--policy-file`,
+`--estimate-cost`, `--with-ui`, `--no-stream`, `--base-url`).
+
+**Logout clears state**: `teardrop auth logout` removes both credentials **and**
+the active thread id from the config file. The next `teardrop chat` after logout
+will start a fresh thread.
+
+---
+
+## Schedules
+
+Recurring interval-based runs:
+
+```bash
+teardrop schedules create \
+  --name hourly-briefing \
+  --prompt "Summarize open incidents" \
+  --interval-seconds 3600
+
+teardrop schedules list
+teardrop schedules get <schedule-id>
+teardrop schedules update <schedule-id> --enabled false
+teardrop schedules update <schedule-id> --clear-callback-url
+teardrop schedules runs <schedule-id> --limit 50 --json
+teardrop schedules delete <schedule-id>
+teardrop schedules delete <schedule-id> --yes
+```
+
+Non-JSON list output includes: `ID`, `Name`, `Enabled`, `Interval`, `Consecutive Failures`, `Last Run At`.
+
+Run history output includes: `Run ID`, `Status`, `Cost (USDC)`, `Error Message`, `Executed At`.
+
+`--clear-callback-url` sends an explicit `null` callback URL while still preserving PATCH semantics for all other omitted fields.
+
+---
+
+## Event Triggers
+
+Reactive runs exposed as signed public webhook endpoints:
+
+```bash
+teardrop event-triggers create \
+  --name inbound-orders \
+  --prompt "Validate and process this order payload"
+
+teardrop event-triggers list
+teardrop event-triggers get <trigger-id>
+teardrop event-triggers update <trigger-id> --enabled false
+teardrop event-triggers update <trigger-id> --callback-url https://example.com/hook
+teardrop event-triggers runs <trigger-id> --limit 50 --json
+teardrop event-triggers rotate-secret <trigger-id>
+teardrop event-triggers delete <trigger-id>
+teardrop event-triggers delete <trigger-id> --yes
+```
+
+`create` and `rotate-secret` display the signing secret once. Store it immediately; subsequent `list` and `get` calls do not return the plaintext secret.
+
+Non-JSON list output includes: `ID`, `Name`, `Enabled`, `Kind`, `Consecutive Failures`, `Last Run At`.
+
+Run history output includes: `Run ID`, `Status`, `Cost (USDC)`, `Error Message`, `Executed At`.
+
+---
+
 ## Billing & Credits
 
 ```bash
@@ -134,17 +219,30 @@ Example `tool.json`:
 {
   "name": "get_weather",
   "description": "Fetch current weather conditions for a given city.",
-  "webhook_url": "https://api.example.com/webhooks/teardrop",
   "input_schema": {
     "type": "object",
     "properties": {
       "city": { "type": "string", "description": "City name, e.g. 'London'" }
     },
-    "required": ["city"]
+    "required": ["city"],
+    "additionalProperties": false
   },
+  "output_schema": {
+    "type": "object",
+    "properties": {
+      "result": { "type": "string", "description": "Weather summary for the requested city." }
+    },
+    "required": ["result"],
+    "additionalProperties": true
+  },
+  "webhook_url": "https://api.example.com/webhooks/teardrop",
+  "webhook_method": "GET",
+  "auth_header_name": null,
+  "auth_header_value": null,
   "timeout_seconds": 10,
   "publish_as_mcp": true,
   "marketplace_description": "Real-time weather data for any city worldwide.",
+  "category": "data",
   "base_price_usdc": 5000
 }
 ```

{teardrop_cli-0.1.1 → teardrop_cli-0.3.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "teardrop-cli"
-version = "0.1.1"
+version = "0.3.0"
 description = "Command-line interface for the Teardrop AI agent platform"
 readme = "README.md"
 license = { file = "LICENSE" }
@@ -24,7 +24,7 @@ classifiers = [
     "Topic :: Software Development :: Libraries :: Python Modules",
 ]
 dependencies = [
-    "teardrop-sdk>=0.1.5",
+    "teardrop-sdk>=0.2.0",
     "typer>=0.12",
     "rich>=13.0",
     "platformdirs>=4.0",

{teardrop_cli-0.1.1 → teardrop_cli-0.3.0}/src/teardrop_cli/_fixtures.py

@@ -176,9 +176,9 @@ def make_benchmarks_response(models: list[dict] | None = None) -> MagicMock:
                 "supports_streaming": True,
                 "quality_tier": 2,
                 "pricing": {
-                    "tokens_in_cost_per_1k": 0.08,
-                    "tokens_out_cost_per_1k": 0.24,
-                    "tool_call_cost": 0.0,
+                    "tokens_in_cost_per_1k": 1_250.0,
+                    "tokens_out_cost_per_1k": 6_250.0,
+                    "tool_call_cost": 1_000.0,
                 },
                 "benchmarks": {
                     "total_runs_7d": 1250,
@@ -195,3 +195,57 @@ def make_benchmarks_response(models: list[dict] | None = None) -> MagicMock:
     obj.models = models
     obj.updated_at = data["updated_at"]
     return obj
+
+
+def make_pricing_response(
+    base_cost_usdc: int = 500,
+    tools: list[dict] | None = None,
+) -> MagicMock:
+    """Return a minimal BillingPricingResponse-like mock."""
+    if tools is None:
+        tools = [
+            {
+                "tool_name": "acme/weather",
+                "price_usdc": 5000,
+                "description": "Get the weather",
+            }
+        ]
+    data = {"tools": tools, "base_cost_usdc": base_cost_usdc, "updated_at": "2026-04-16T12:00:00Z"}
+    obj = MagicMock()
+    obj.model_dump = lambda: dict(data)
+    obj.tools = tools
+    obj.base_cost_usdc = base_cost_usdc
+    obj.updated_at = data["updated_at"]
+    return obj
+
+
+def make_credit_history_entries(
+    count: int = 3,
+) -> list[MagicMock]:
+    """Return a list of CreditHistoryEntry-like mocks.
+
+    Each mock has a ``model_dump`` method so the CLI can normalise it, matching
+    the real SDK's ``list[CreditHistoryEntry]`` return type.
+    """
+    entries = []
+    samples = [
+        {"reason": "Subscription fee — acme/weather", "amount_usdc": 5000, "operation": "debit"},
+        {"reason": "Top-up", "amount_usdc": 50_000_000, "operation": "topup"},
+        {"reason": "Agent run — code review", "amount_usdc": 1250, "operation": "debit"},
+    ]
+    for i in range(count):
+        base = samples[i % len(samples)]
+        data = {
+            "id": f"ch_{i}",
+            "amount_usdc": base["amount_usdc"],
+            "operation": base["operation"],
+            "balance_usdc_after": 100_000_000 - base["amount_usdc"] * (i + 1),
+            "reason": base["reason"],
+            "created_at": f"2026-06-{10 - i:02d}T12:00:00Z",
+        }
+        obj = MagicMock()
+        obj.model_dump = lambda d=data: dict(d)
+        for k, v in data.items():
+            setattr(obj, k, v)
+        entries.append(obj)
+    return entries

teardrop_cli-0.3.0/src/teardrop_cli/_templates.py

@@ -0,0 +1,51 @@
+"""In-package templates for ``teardrop tools init``."""
+
+from __future__ import annotations
+
+# Complete starter template matching CreateOrgToolRequest schema.
+# All fields are explicit --- nullable fields use None so they appear as
+# ``null`` in the output JSON and users discover them early.
+_BASE_TEMPLATE = {
+    "name": "{name}",
+    "description": "Short one-line summary of what this tool does.",
+    "input_schema": {
+        "type": "object",
+        "properties": {
+            "query": {
+                "type": "string",
+                "description": "Example input field. Replace with your real schema.",
+            }
+        },
+        "required": ["query"],
+        "additionalProperties": False,
+    },
+    "output_schema": {
+        "type": "object",
+        "properties": {
+            "result": {
+                "type": "string",
+                "description": "Example output field. Replace with your real schema.",
+            }
+        },
+        "required": ["result"],
+        "additionalProperties": True,
+    },
+    "webhook_url": "https://example.com/your-webhook-endpoint",
+    "webhook_method": "GET",
+    "auth_header_name": None,
+    "auth_header_value": None,
+    "timeout_seconds": 10,
+    "publish_as_mcp": False,
+    "marketplace_description": None,
+    "category": "",
+    "base_price_usdc": 0,
+}
+
+
+def render_tool_template(name: str, *, with_marketplace: bool = False) -> dict:
+    """Return a dict suitable for ``json.dumps`` describing a starter tool."""
+    data = {**_BASE_TEMPLATE, "name": name}
+    if with_marketplace:
+        data["publish_as_mcp"] = True
+        data["marketplace_description"] = "One-line marketplace pitch (max 200 characters)."
+    return data

{teardrop_cli-0.1.1 → teardrop_cli-0.3.0}/src/teardrop_cli/cli.py

@@ -18,12 +18,16 @@ from teardrop_cli._lazy import LazyGroup
     cls=LazyGroup,
     lazy_subcommands={
         "auth": "teardrop_cli.commands.auth:app",
+        "chat": "teardrop_cli.commands.chat:app",
         "init": "teardrop_cli.commands.config_cmd:init_app",
         "quickstart": "teardrop_cli.commands.quickstart:app",
         "config": "teardrop_cli.commands.config_cmd:app",
         "run": "teardrop_cli.commands.run:app",
+        "schedules": "teardrop_cli.commands.schedules:app",
         "balance": "teardrop_cli.commands.balance:app",
         "usage": "teardrop_cli.commands.usage:app",
+        "agent-tools": "teardrop_cli.commands.agent_tools:app",
+        "event-triggers": "teardrop_cli.commands.event_triggers:app",
         "marketplace": "teardrop_cli.commands.marketplace:app",
         "tools": "teardrop_cli.commands.tools:app",
         "earnings": "teardrop_cli.commands.earnings:app",