Bring Sim Management
to CrewAI

Each IoT SIM is uniquely identified by its ICCID (Integrated Circuit Card Identifier) -- a 19-20 digit number printed on the SIM card or available in your IoT Control Center dashboard. The ICCID is required for all device-specific operations like activation, suspension, and usage queries. You can list all your devices with list_devices to discover ICCIDs for your entire fleet.

Data pools are shared data plans across multiple IoT SIMs. Instead of each SIM having an individual cap, all devices in the pool draw from a common data bucket. Use list_data_pools to see your pools, get_pool_usage to check consumption and identify top-consuming devices, and set up alerts before reaching the limit. If a pool is near exhaustion, you can suspend low-priority devices with suspend_device or migrate high-usage devices to a different pool with update_device_settings.

Yes. Use the diagnose_connectivity tool with the device's ICCID. It runs automated checks for network registration status, APN configuration, active data session, signal strength, and known network outages in the device's area. The tool returns detailed diagnostic results with recommended actions -- helping your field engineers resolve connectivity issues without manual portal navigation.

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.