send_shell_command
Send a shell command to a device (SIM card or web agent) for immediate execution.
Send a shell command to a device (SIM card or web agent) for immediate execution.
Writes data · Calls external systems.
Parameters
| Field | Type | Required | Description |
|---|---|---|---|
command | string | Yes | Command payload as JSON string. Fields depend on action type — use list_shell_action_types for guidance. |
owner | string | Yes | Device identifier: MSISDN for SIM (e.g. 0789800356), hostname for Ethernet (e.g. my-web-agent) |
product_id | number | Yes | Product ID that owns the device |
type | string | Yes | Action type (e.g. USSD, ETH_HTTP_API, DATA_PING). Use list_shell_action_types to see options. |
Example arguments
Illustrative arguments an agent supplies when calling this tool:
{
"product_id": 0,
"owner": "string",
"type": "string",
"command": "string"
}Description
PREREQUISITE: call platform_guide topic=shell for USSD navigation, resource contention handling, and async event patterns. Unlike tests, shell commands have no assertions — they fire a command and return the raw result. Use list_shell_action_types to discover available action types and their required command fields. Returns the shell ID for polling with get_shell_result. USSD is session-based: dial the root shortcode first (e.g. {"input":"*199#"}), then check get_shell_result — if session is OPEN, send follow-up menu options as separate commands (e.g. {"input":"1"}, {"input":"2"}). Prefer step-by-step navigation over long shortcodes like *199*5# — only use long shortcodes when the user explicitly provides one. Sessions expire after ~30s.Related
What's next?
Last updated on