Skip to main content
Glama
134,408 tools. Last updated 2026-05-23 19:26

"How to Control Tuya Smart IoT Devices" matching MCP tools:

  • Get recent Hyperliquid perpetual futures trades from Smart Traders and Funds across all tokens. This tool provides granular smart trader and funds activity. For a big picture view of smart traders and funds activity across all tokens, use token_discovery_screener with traderType="sm" filter. **Note:** This endpoint is Hyperliquid-only (perpetual futures data). It returns recent trades only (no date filtering available). Columns returned: - **Time**: Timestamp when the trade occurred (datetime: YYYY-MM-DD HH:MM:SS) - **Side**: Position direction - Long or Short - **Action**: Order action - Add, Reduce, Open, Close - **Token**: Symbol of the perpetual contract - **Size**: Quantity of the perpetual contract (numeric) - **Price USD**: Price per token at time of trade (price formatted) - **Value USD**: Total USD value of the trade (currency formatted) - **Trader**: Nansen label of the trading address - **Tx Hash**: Blockchain transaction hash for verification Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, valueUsd, amount, priceUsd Examples: # Get recent smart money perp trades (sorted by value) ``` { "order_by": "valueUsd", "order_by_direction": "desc" } ``` # Filter by action and side ``` { "action": "Open", "side": "Long", "includeSmartMoneyLabels": ["Fund", "All Time Smart Trader"] } ```
    Connector
  • List every signing key registered on the artist's account — active and revoked. Multi-device support: each iPhone the artist signs from has its own key under the same DID. Use this to triage "I think I lost a phone" or "show me my devices." The response also carries `has_signing_genesis` (boolean). Use it to route the artist correctly: if `has_signing_genesis` is FALSE, the account has NEVER paired a signing device — there is no key to lose and no recovery to run; the artist must pair their first iPhone. That flow is desktop-initiated and runs inline the first time they authenticate a work — tell them to open Raisonnai on their computer, not the iPhone app (no app session exists yet). If `has_signing_genesis` is TRUE but every key in `items` is revoked, the account paired before and lost all devices — that is account recovery, not pairing; tell them to start recovery from Raisonnai. Never conflate these two states. TRIGGER: "list my signing keys," "what devices can authenticate for me," "show my signing devices."
    Connector
  • List all attributes (properties) of a specific Smart Data Model, including each attribute's NGSI type (Property, GeoProperty, or Relationship), data type, description, recommended units, and reference model URL. Use this after get_data_model when the user wants to understand what fields a model has, what values they accept, or how to construct a valid NGSI-LD payload. Example: get_attributes_for_model({"model_name": "WeatherObserved"})
    Connector
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use workspace.search for that.
    Connector
  • List devices registered in the workspace. Returns a list of Device objects with id, name, status, last_heartbeat, platform/hardware info, tags, and created_at. ``status`` is ``online`` if a heartbeat was received within the last 5 minutes, otherwise ``offline`` (or ``unknown`` for devices that have never reported). Requires the ``device:read`` scope. Device-scoped api_keys cannot call this endpoint and will receive 403.
    Connector
  • Trigger a health check for a specific smart link. Checks the default URL and all geo-rule URLs for availability. Returns the health status (healthy/broken/unknown). Rate limited to once per 5 minutes per link. Does NOT modify the link configuration. Common errors: - Rate limit: wait 5 minutes between health checks for the same link. - Smart link not found: check the ID.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Find relevant Smart‑Thinking memories fast. Fetch full entries by ID to get complete context. Spee…

  • Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.

  • Get information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.
    Connector
  • Explain the Guard product using CurrencyGuard's approved product and FAQ content. Covers: what the Guard is, how it works, who it is for, how it compares to forwards or options, and legal, regulatory, accounting, or eligibility questions.
    Connector
  • Get 25 token transfers (per page) for a specific token based on the sort order. Default is most recent transfers first. **NOTE:** This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee). Columns returned: - **Time**: Timestamp when the transfer occurred (block_timestamp: ISO 8601 format) - **From Label**: Source address label (from_address_label: sender of tokens) - **To Label**: Destination address label (to_address_label: receiver of tokens) - **From Address**: Raw source address (from_address: hex address) - **To Address**: Raw destination address (to_address: hex address) - **Amount**: Quantity of tokens transferred (transfer_amount: numeric) - **Value USD**: USD value of the transfer at time of transaction (transfer_value_usd: currency formatted) - **Type**: Transfer category (transaction_type: DEX, CEX, transfer, etc.) - **Tx Hash**: Blockchain transaction hash for verification (transaction_hash) Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, amount, valueUsd Examples: # Basic request (most recent transfers first) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "order_by": "timestamp", "order_by_direction": "desc" } ``` # Smart money only filter (largest transfers first) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "transferOriginCategories": ["all_transfers"], "onlySmartTradersAndFunds": true, "order_by": "valueUsd", "order_by_direction": "desc" } ``` # Filter by DEX only with minimum transfer value (USD) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "transferOriginCategories": ["dex"], "transferValueUsd": {"from": 1000} } ``` # Filter transfers sent FROM a specific wallet ``` { "chain": "base", "tokenAddress": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "dateRange": {"from": "2025-03-12", "to": "2025-03-12"}, "fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "order_by": "timestamp", "order_by_direction": "desc" } ``` **Available Filters:** Address Filters: - **fromAddress** (str or list[str], optional): Filter by sender address(es) Example: "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72" Example: ["0xaddr1", "0xaddr2"] - **toAddress** (str or list[str], optional): Filter by recipient address(es) Use fromAddress/toAddress when looking for a specific wallet's transfers. Transfer Origin Categories: - **transferOriginCategories** (list[str]): List of transfer types to include Possible values: ['dex', 'cex', 'non_exchange_transfers', 'all_transfers'] Default: ['all_transfers'] Examples: - ['dex'] - only DEX transfers - ['cex'] - only CEX transfers - ['dex', 'cex'] - both DEX and CEX - ['non_exchange_transfers'] - only non-exchange transfers - ['all_transfers'] - all types (default) Smart Money Filter: - **onlySmartTradersAndFunds** (bool): Only show smart money transfers (default: false) When true, filters to show **only** transfers involving profitable addresses Numeric Range Filter: - **transferValueUsd** (object, optional): Filter by USD value of transfer Format: {"from": X, "to": Y} or {"from": X} or {"to": Y} - Specify only `from` for minimum bound (no maximum) - Specify only `to` for maximum bound (no minimum) - Specify both for a bounded range Example: {"from": 1000} - only transfers worth at least $1,000 USD Example: {"to": 50000} - only transfers up to $50,000 USD Example: {"from": 1000, "to": 50000} - transfers between $1,000 and $50,000 USD Note: This filters by the USD value of the transfer at time of transaction Notes: - Use fromAddress/toAddress to find transfers for a specific wallet - Use transferOriginCategories to control which transfer origins are included - Smart Money filter shows **only** transfers involving profitable addresses (definition of *Smart Money*) - transferValueUsd filters by USD value at time of transaction
    Connector
  • Delete a smart link permanently. The short URL will stop working. IMPORTANT: Always confirm with the user before executing this action. The `confirm` parameter must be set to true. This is a destructive action that cannot be undone — the slug becomes available for reuse after a cooldown period. Does NOT affect other links or YouTube descriptions. Common errors: - Smart link not found: check the ID. - confirm=False: you must set confirm=True after getting user confirmation.
    Connector
  • Returns the list of supported measurement devices (CMMs, scanners), file formats, and system requirements for DezignWorks. Use to check hardware compatibility before recommending the product.
    Connector
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use workspace.search for that.
    Connector
  • Get information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.
    Connector
  • Patch a single chart in an existing dashboard by chart ID. Provide only the chart fields to change. Set a field to null to remove it. Use overwrite=true to skip version conflict checks, or provide the current dashboard version for optimistic concurrency control.
    Connector
  • Validate a JSON payload against the schema of a specific Smart Data Model. Use this when the user has an IoT payload or NGSI-LD entity and wants to check if it conforms to the standard. Returns a structured result with pass/fail and a list of specific validation errors if any. Example: validate_data({"model_name": "WeatherObserved", "data": {"id": "urn:ngsi-ld:WeatherObserved:001", "type": "WeatherObserved", "temperature": {"type": "Property", "value": 22.3}}})
    Connector
  • The MITRE Rosetta Stone. Given a MITRE technique ID across 5 frameworks (ATT&CK Enterprise, ATT&CK Mobile, ATT&CK ICS, D3FEND, ATLAS), return the Bidda node for that technique plus its mapped compliance obligations: NIST 800-53 controls, ISO 27001 Annex A clauses, PCI DSS requirements, NIS2 articles, HIPAA Security Rule, DORA articles, NERC CIP, IEC 62443. The bridge between how SOC teams think (technique IDs) and how compliance teams think (control families). Free.
    Connector
  • Update an existing smart link (partial update — only provided fields change). You can update the destination URL, slug, title, redirect type, geo rules, or deep link config. Geo rules are replaced entirely (not merged). Does NOT delete the link. Common errors: - Smart link not found: check the ID. - Slug already taken: choose a different slug.
    Connector
  • Get recent Hyperliquid perpetual futures trades from Smart Traders and Funds across all tokens. This tool provides granular smart trader and funds activity. For a big picture view of smart traders and funds activity across all tokens, use token_discovery_screener with traderType="sm" filter. **Note:** This endpoint is Hyperliquid-only (perpetual futures data). It returns recent trades only (no date filtering available). Columns returned: - **Time**: Timestamp when the trade occurred (datetime: YYYY-MM-DD HH:MM:SS) - **Side**: Position direction - Long or Short - **Action**: Order action - Add, Reduce, Open, Close - **Token**: Symbol of the perpetual contract - **Size**: Quantity of the perpetual contract (numeric) - **Price USD**: Price per token at time of trade (price formatted) - **Value USD**: Total USD value of the trade (currency formatted) - **Trader**: Nansen label of the trading address - **Tx Hash**: Blockchain transaction hash for verification Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, valueUsd, amount, priceUsd Examples: # Get recent smart money perp trades (sorted by value) ``` { "order_by": "valueUsd", "order_by_direction": "desc" } ``` # Filter by action and side ``` { "action": "Open", "side": "Long", "includeSmartMoneyLabels": ["Fund", "All Time Smart Trader"] } ```
    Connector
  • Get full details of a single smart link by ID. Returns all configuration including geo rules, deep link config, and click stats. Does NOT modify the link. Common errors: - Smart link not found: check the ID or use `youfiliate_list_smart_links`.
    Connector
  • Search FDA Pre-Market Approval (PMA) records across all companies. PMA is required for high-risk (Class III) devices. Filter by company name (fuzzy match), product code, and date range. Returns PMA number, applicant, trade name, decision date, and product code. Related: fda_device_class (product code details), fda_search_510k (510(k) clearances for lower-risk devices), fda_product_code_lookup (cross-reference a product code).
    Connector