@wowok/agent-mcp 2.2.13 → 2.2.14

package/docs/skills/schema-guard2file.md

@@ -1,153 +0,0 @@
-# Guard2File Tool Schema
-
-> **Tool Name**: `guard2file`
-> **Description**: Export a Guard object's definition from the blockchain to a local JSON or Markdown file for editing and creating new Guard objects. Note: To query on-chain object information, use the 'query_toolkit' tool instead.
-
----
-
-## Tool Schema
-
-```typescript
-guard2file: Guard2File_Input
-```
-
----
-
-## Input Schema
-
-```typescript
-Guard2File_Input {
-  guard: NameOrAddress,           // REQUIRED - Guard object ID or name to export
-  file_path: string,              // REQUIRED - Output file path (absolute or relative)
-  format?: "json" | "markdown",   // OPTIONAL - Output format (default: 'json')
-  env?: CallEnv                   // OPTIONAL - Environment configuration
-}
-```
-
----
-
-## Sub Schemas
-
-### NameOrAddress
-
-```typescript
-NameOrAddress = string           // Object ID (0x prefix + 64 hex chars) or name (max 64 chars)
-```
-
-### CallEnv
-
-```typescript
-CallEnv {
-  account?: NameOrAddress,        // Account/Object name or ID for signing
-  network?: "localnet" | "testnet", // Network entrypoint
-  no_cache?: boolean,             // Whether to disable caching
-  permission_guard?: string[],    // Permission guard IDs for extended permissions
-  referrer?: string               // Referrer ID for first-time network users
-}
-```
-
----
-
-## Output Schema
-
-```typescript
-Guard2File_OutputWrapped {
-  result: Guard2File_Output       // Guard2File operation output
-}
-
-Guard2File_Output =
-  | { status: "success"; data: Guard2File_SuccessData }
-  | { status: "error"; error: string }
-```
-
-### Success Data
-
-```typescript
-Guard2File_SuccessData {
-  file_path: string,              // Absolute path of the exported file
-  format: "json" | "markdown",    // Export format
-  guard_object: string            // Guard object ID
-}
-```
-
----
-
-## Usage Guide
-
-### Purpose
-
-The `guard2file` tool is specifically designed to:
-1. Export an existing Guard object's definition from the blockchain
-2. Save it to a local file for editing
-3. Use the exported file to create new Guard objects
-
-### When to Use
-
-| Scenario | Tool to Use |
-|----------|-------------|
-| Export Guard for editing | `guard2file` |
-| Query Guard on-chain state | `query_toolkit` |
-| Create new Guard | `onchain_operations` (guard) |
-| Modify existing Guard | `onchain_operations` (guard) |
-
-### File Formats
-
-**JSON Format** (`format: "json"`):
-- Machine-readable format
-- Suitable for programmatic processing
-- Default format
-
-**Markdown Format** (`format: "markdown"`):
-- Human-readable format with comments
-- Suitable for manual editing
-- Includes documentation
-
----
-
-## Example
-
-```typescript
-// Export a Guard to JSON file
-guard2file: {
-  guard: "0x1234...abcd",         // Guard object ID
-  file_path: "./my_guard.json",   // Output path
-  format: "json"
-}
-
-// Export a Guard to Markdown file
-guard2file: {
-  guard: "my_guard_name",         // Guard name
-  file_path: "./my_guard.md",     // Output path
-  format: "markdown"
-}
-```
-
----
-
-## Output Examples
-
-### Success Response
-
-```json
-{
-  "result": {
-    "status": "success",
-    "data": {
-      "file_path": "/absolute/path/to/my_guard.json",
-      "format": "json",
-      "guard_object": "0x1234567890abcdef..."
-    }
-  }
-}
-```
-
-### Error Response
-
-```json
-{
-  "result": {
-    "status": "error",
-    "error": "Guard object not found: 0x1234..."
-  }
-}
-```

package/docs/skills/schema-local_info_operation.md

@@ -1,160 +0,0 @@
-# Schema: local_info_operation
-
-> 100% LOCAL, NEVER ON-CHAIN - Manage sensitive personal information stored ONLY on your device: delivery addresses, phone numbers, contacts.
-
----
-
-## Top-Level Structure
-
-```typescript
-LocalInfoOperation {
-  // Exactly ONE operation type must be specified
-  add?: AddOperation;
-  remove?: RemoveOperation;
-  reset?: ResetOperation;
-  clear?: ClearOperation;
-}
-```
-
----
-
-## Operation Types
-
-### add
-
-Add one or more info entries.
-
-```typescript
-AddOperation {
-  op: "add";
-  data: InfoData[];  // At least 1 item required
-}
-
-InfoData {
-  name: string;       // Unique identifier (max 64 bcs characters)
-  default: string;    // Primary/default value (max 300 bcs characters)
-  contents?: string[]; // Additional values (max 50 items, each max 300 bcs)
-  createdAt?: number; // Unix timestamp (ms)
-  updatedAt?: number; // Unix timestamp (ms)
-}
-```
-
-**Result**:
-
-```typescript
-AddResult {
-  success: boolean;
-}
-```
-
----
-
-### remove
-
-Remove info entries by name.
-
-```typescript
-RemoveOperation {
-  op: "remove";
-  data: string[];     // Array of info names to remove (at least 1)
-}
-```
-
-**Result**:
-
-```typescript
-RemoveResult {
-  success: boolean;
-}
-```
-
----
-
-### reset
-
-Reset the contents of an existing info entry.
-
-```typescript
-ResetOperation {
-  op: "reset";
-  name: string;       // Name of info entry to reset
-  contents: string[]; // New content list to replace existing
-}
-```
-
-**Result**:
-
-```typescript
-ResetResult {
-  success: boolean;
-}
-```
-
----
-
-### clear
-
-Remove all info entries.
-
-```typescript
-ClearOperation {
-  op: "clear";
-}
-```
-
-**Result**:
-
-```typescript
-ClearResult {
-  success: boolean;
-}
-```
-
----
-
-## Output Structure
-
-```typescript
-LocalInfoOperationOutput {
-  status: "success" | "error";
-  data?: LocalInfoOperationResult;  // Present when status = "success"
-  error?: string;                   // Present when status = "error"
-}
-
-LocalInfoOperationResult {
-  success: boolean;
-}
-
-// Wrapped format
-{
-  result: LocalInfoOperationOutput;
-}
-```
-
----
-
-## Query Local Info List
-
-```typescript
-QueryLocalInfoList {
-  filter?: LocalInfoFilter;
-}
-
-LocalInfoFilter {
-  name?: string;              // Filter by info name (fuzzy match)
-  default?: string;           // Filter by default value (fuzzy match)
-  contents?: string[];        // Filter by contents (contains ANY of specified)
-  createdAt?: {
-    gte?: number;             // Created on or after (ms)
-    lte?: number;             // Created on or before (ms)
-  };
-  updatedAt?: {
-    gte?: number;             // Updated on or after (ms)
-    lte?: number;             // Updated on or before (ms)
-  };
-}
-
-QueryLocalInfoListResult {
-  result: InfoData[];
-}
-```

package/docs/skills/schema-local_mark_operation.md

@@ -1,148 +0,0 @@
-# Schema: local_mark_operation
-
-> 100% LOCAL, NEVER ON-CHAIN - Manage ID names and tags stored ONLY on your local device for easy identification of user address or object IDs by name.
-
----
-
-## Top-Level Structure
-
-```typescript
-LocalMarkOperation {
-  // Exactly ONE operation type must be specified
-  add?: AddOperation;
-  remove?: RemoveOperation;
-  clear?: ClearOperation;
-}
-```
-
----
-
-## Operation Types
-
-### add
-
-Add one or more marks.
-
-```typescript
-AddOperation {
-  op: "add";
-  data: MarkParam[];  // At least 1 item required
-}
-
-MarkParam {
-  address: string;    // Valid ID: 0x prefix + 64 hex chars, or builtin ID
-  name?: {
-    value: string;    // Mark name (max 64 bcs characters)
-    replaceExistName?: boolean;  // Replace existing mark with same name
-  };
-  tags?: string[];    // Max 50 tags, each max 64 bcs characters
-}
-```
-
-**Result**:
-
-```typescript
-AddResult {
-  add: MarkData[];    // List of added mark data
-}
-
-MarkData {
-  name?: string;      // Mark name (max 64 bcs characters)
-  address: string;    // Valid ID
-  tags?: string[];    // Tags for categorization
-  createdAt?: number; // Unix timestamp (ms)
-  updatedAt?: number; // Unix timestamp (ms)
-}
-```
-
----
-
-### remove
-
-Remove marks by name or address.
-
-```typescript
-RemoveOperation {
-  op: "remove";
-  names: string[];    // Array of mark names or addresses to remove (at least 1)
-}
-```
-
-**Result**:
-
-```typescript
-RemoveResult {
-  remove: MarkData[];  // List of removed mark data
-}
-```
-
----
-
-### clear
-
-Remove all marks.
-
-```typescript
-ClearOperation {
-  op: "clear";
-}
-```
-
-**Result**:
-
-```typescript
-ClearResult {
-  clear: boolean;     // Whether all marks were successfully removed
-}
-```
-
----
-
-## Output Structure
-
-```typescript
-LocalMarkOperationOutput {
-  status: "success" | "error";
-  data?: LocalMarkOperationResult;  // Present when status = "success"
-  error?: string;                   // Present when status = "error"
-}
-
-LocalMarkOperationResult {
-  add?: MarkData[];
-  remove?: MarkData[];
-  clear?: boolean;
-}
-
-// Wrapped format
-{
-  result: LocalMarkOperationOutput;
-}
-```
-
----
-
-## Query Local Mark List
-
-```typescript
-QueryLocalMarkList {
-  filter?: LocalMarkFilter;
-}
-
-LocalMarkFilter {
-  name?: string;              // Filter by mark name (fuzzy match)
-  tags?: string[];            // Filter by tags (contains ANY of specified)
-  address?: string;           // Filter by address (exact match)
-  createdAt?: {
-    gte?: number;             // Created on or after (ms)
-    lte?: number;             // Created on or before (ms)
-  };
-  updatedAt?: {
-    gte?: number;             // Updated on or after (ms)
-    lte?: number;             // Updated on or before (ms)
-  };
-}
-
-QueryLocalMarkListResult {
-  result: MarkData[];
-}
-```

package/docs/skills/schema-machineNode2file.md

@@ -1,155 +0,0 @@
-# MachineNode2File Tool Schema
-
-> **Tool Name**: `machineNode2file`
-> **Description**: Export a Machine object's node definition from the blockchain to a local JSON or Markdown file for editing and creating new Machine objects. Note: To query on-chain object information, use the 'query_toolkit' tool instead.
-
----
-
-## Tool Schema
-
-```typescript
-machineNode2file: MachineNode2File_Input
-```
-
----
-
-## Input Schema
-
-```typescript
-MachineNode2File_Input {
-  machine: NameOrAddress,         // REQUIRED - Machine object ID or name to export
-  file_path: string,              // REQUIRED - Output file path (absolute or relative)
-  format?: "json" | "markdown",   // OPTIONAL - Output format (default: 'json')
-  env?: CallEnv                   // OPTIONAL - Environment configuration
-}
-```
-
----
-
-## Sub Schemas
-
-### NameOrAddress
-
-```typescript
-NameOrAddress = string           // Object ID (0x prefix + 64 hex chars) or name (max 64 chars)
-```
-
-### CallEnv
-
-```typescript
-CallEnv {
-  account?: NameOrAddress,        // Account/Object name or ID for signing
-  network?: "localnet" | "testnet", // Network entrypoint
-  no_cache?: boolean,             // Whether to disable caching
-  permission_guard?: string[],    // Permission guard IDs for extended permissions
-  referrer?: string               // Referrer ID for first-time network users
-}
-```
-
----
-
-## Output Schema
-
-```typescript
-MachineNode2File_OutputWrapped {
-  result: MachineNode2File_Output // MachineNode2File operation output
-}
-
-MachineNode2File_Output =
-  | { status: "success"; data: MachineNode2File_SuccessData }
-  | { status: "error"; error: string }
-```
-
-### Success Data
-
-```typescript
-MachineNode2File_SuccessData {
-  file_path: string,              // Absolute path of the exported file
-  format: "json" | "markdown",    // Export format
-  machine_object: NameOrAddress,  // Machine object ID
-  node_count: number              // Number of nodes exported
-}
-```
-
----
-
-## Usage Guide
-
-### Purpose
-
-The `machineNode2file` tool is specifically designed to:
-1. Export an existing Machine object's node definition from the blockchain
-2. Save it to a local file for editing
-3. Use the exported file to create new Machine objects
-
-### When to Use
-
-| Scenario | Tool to Use |
-|----------|-------------|
-| Export Machine nodes for editing | `machineNode2file` |
-| Query Machine on-chain state | `query_toolkit` |
-| Create new Machine | `onchain_operations` (machine) |
-| Modify existing Machine nodes | `onchain_operations` (machine) |
-
-### File Formats
-
-**JSON Format** (`format: "json"`):
-- Machine-readable format
-- Suitable for programmatic processing
-- Default format
-
-**Markdown Format** (`format: "markdown"`):
-- Human-readable format with comments
-- Suitable for manual editing
-- Includes documentation
-
----
-
-## Example
-
-```typescript
-// Export a Machine's nodes to JSON file
-machineNode2file: {
-  machine: "0x1234...abcd",       // Machine object ID
-  file_path: "./my_machine.json", // Output path
-  format: "json"
-}
-
-// Export a Machine's nodes to Markdown file
-machineNode2file: {
-  machine: "my_machine_name",     // Machine name
-  file_path: "./my_machine.md",   // Output path
-  format: "markdown"
-}
-```
-
----
-
-## Output Examples
-
-### Success Response
-
-```json
-{
-  "result": {
-    "status": "success",
-    "data": {
-      "file_path": "/absolute/path/to/my_machine.json",
-      "format": "json",
-      "machine_object": "0x1234567890abcdef...",
-      "node_count": 5
-    }
-  }
-}
-```
-
-### Error Response
-
-```json
-{
-  "result": {
-    "status": "error",
-    "error": "Machine object not found: 0x1234..."
-  }
-}
-```