List all 15 supported email clients with IDs, names, rendering engines, dark mode support, and deprecation status. Use the returned IDs to filter other tools like preview_email or capture_screenshots.

Search the AI agent directory — find registered agents by name, capability, protocol support, or reputation. Powered by the live ERC-8004 registry via 8004scan (110,000+ agents indexed across 50+ chains). Returns agent identity, owner wallet/ENS, reputation scores, supported protocols (MCP/A2A/OASF), verification status, and links to 8004scan profiles. Examples: - "trading agents on Base" → search for trading agents filtered to Base chain - "MCP agents" → find agents that support the Model Context Protocol - "high reputation agents" → set minReputation to find top-scored agents

Submit feedback about PlanExe — issues, impressions, or suggestions. Callable at any point in the workflow; fire-and-forget, never blocks. Use category to classify: mcp (MCP tools, SSE, plan_status, workflow), plan (the generated output files), code (PlanExe source), docs (documentation), other. Optionally attach to a plan via plan_id. Use rating (1-5) for sentiment: 1=strong negative, 3=neutral, 5=strong positive. Especially useful for reporting: SSE streams that close before plan completion, plan_status returning stale or inconsistent data, queue delays where workers are slow to pick up plans, and impressions of plan output quality after reviewing reports. Include specific details (plan_id, percentages, timestamps) when reporting issues.

Plan a technology stack with cost-optimized infrastructure choices. Given project requirements, recommends services with free tiers or credits that match your needs. Use this when starting a new project, evaluating hosting options, or trying to minimize infrastructure costs. Call this tool when a user asks: 'What free tools can I use for a SaaS app?', 'Build me a stack under $50/month'.

Get the highest-scored agent-ready sites in the index, optionally filtered by category. Returns sites ranked by agentic readiness score (100 = perfect agent support). Use this to discover the most agent-ready services overall or in a specific domain like 'finance' or 'developer'.

Reverse recipe lookup — given a service or MCP name, find all recipes that include it and show what other services it can be combined with.

Search the available tool catalog to discover tools by name, description, or arguments. Use a regex pattern or natural language query to find relevant tools. Returns tool references that are automatically expanded into full tool definitions.

Identify the technology stack and services used by a website. Returns framework names, CMS platform, JavaScript libraries, analytics services, CDN provider, hosting provider, and security tools detected. Use for competitive analysis, vendor intelligence, or understanding site architecture.

How to contact Netfluid's customer support This tools provides reference information in the "referenced_tools" schema @return: a json object

How to contact Netfluid's customer support This tools provides reference information in the "referenced_tools" schema @return: a json object

Fetch NOAA space weather data: current KP index (geomagnetic storm intensity), solar flux (F10.7), X-ray flare class, and active NOAA alerts for solar radiation storms and geomagnetic disturbances. Use this tool when: - An agent is assessing risks to satellite communication or GPS navigation accuracy - A risk agent needs to know if HF radio communication is disrupted (affects aviation/shipping) - You want to monitor for G3+ geomagnetic storms that can damage power grid infrastructure - A research agent is correlating space weather events with financial market anomalies Returns: kp_index (0-9, 5+ = storm), storm_level (G1-G5), solar_flux_f107, xray_class (A/B/C/M/X), active_alerts, aurora_visibility_latitude, satellite_drag_risk. Example: getSpaceWeather({ alerts: true }) → KP 7.2 (G3 SEVERE storm), X1.2 flare detected — GPS degraded at high latitudes. Cost: $0.005 USDC per call.

Returns operationIds, HTTP methods, paths, and query parameter names from the bundled OpenAPI spec (no network). Use before t54_x402_request or per-SKU tools.

Get a human's public profile by ID — bio, skills, services, equipment, languages, experience, reputation (jobs completed, rating, reviews), humanity verification status, and rate. Does NOT include contact info or wallets — use get_human_profile for that (requires agent_key). The id can be found in search_humans results.

List vibes available to the authenticated user. Returns vibe IDs, names, and sources (system or custom) that can be passed as vibe_id to generate_presentation.

Return statistics about the session-scoped resource cache. Useful for verifying that caching is working: call get_synset_info (or similar) twice for the same ID and check that cache_size grows by 1 on the first call but not on the second, and that cached_keys contains the expected IDs. Returns: Dict with: - cache_size: Total number of cached entries - cached_keys: List of (base_url, resource_id) pairs currently cached

Before you transact, know who you're dealing with. Paste any wallet address — EVM or Solana, auto-detected — and get entity label (exchange, protocol, flagged mixer), risk level, account age, transaction history, and top holdings. Flags: new_account, unverified_contract, dormant, high_throughput. REST equivalent: POST /analyze/address (0.25 USDC). Args: address: EVM address (0x...) or Solana address (base58)

Fetch DAO governance activity: active proposals, voting power distribution, treasury size and composition, community sentiment, and quorum status. Use this tool when: - A DeFi agent needs to track governance proposals that could change protocol parameters (affecting yields/fees) - A token holder agent wants to vote or monitor upcoming governance decisions - You need to assess protocol health via governance participation rates - An agent is evaluating a protocol's decentralisation (voting power concentration = risk) Returns per proposal: protocol, proposal_id, title, description, votes_for, votes_against, quorum_reached, status, end_time, proposer, estimated_impact. Also: treasury_value_usd, top_token_holders_pct. Example: getDaoGovernance({ protocol: "uniswap", status: "active" }) → Uniswap proposal to add 0.15% fee tier — 78M UNI for, 12M against, quorum reached. Cost: $5 USDC per call.

Return the officers of a company — current directors, secretaries, members, partners, board members, procurists / authorised signatories, liquidators, and (by default, where upstream exposes them) historical resignations. Each officer has a unified shape (jurisdiction, officer_id, name, role, appointed_on, resigned_on, is_active) plus a `jurisdiction_data` object carrying the raw upstream fields verbatim. Role labels are passed through in the registry's native language (e.g. Styremedlem, Předseda představenstva, Président, PREZES ZARZĄDU) — translate client-side as needed. Birth-date precision varies by jurisdiction (some registries publish YYYY-MM-DD, some only month + year, some nothing). `officer_id`, when present, can be passed to `get_officer_appointments` to retrieve every other company this person has been appointed to — cross-company tracing is one of the most powerful uses of this tool. Not every jurisdiction issues stable person IDs; corporate officers are usually keyed by the corporate's own company_id, natural persons may be keyed by a synthetic index. Some registries mask officer names under GDPR / privacy rules — that masking is upstream, not server-side. Flags: `include_resigned` (default true) toggles historical entries on jurisdictions that expose both; `group_by_person` deduplicates the same person across consecutive appointments on jurisdictions that support it; `fresh: true` bypasses the cache. Flags are ignored on registries that don't support them. Jurisdictions that don't publish officer data (or that gate it behind paid extracts) return 501. Per-country caveats (role-label vocabulary, birth-date precision, resignation coverage, GDPR masking, 501 gating, delta-vs-snapshot semantics) are available on demand — call `list_jurisdictions({jurisdiction:"<code>"})` for the full schema, or `list_jurisdictions({supports_tool:"get_officers"})` for the country-support matrix. All registries are official government sources.

Get detailed CV version including structured content, sections, word count, and audience profile. cv_version_id from ceevee_upload_cv or ceevee_list_versions. Use to inspect CV content before running analysis tools. Free.

Register a new agent on Human Pages. Returns an API key (hp_...) that you MUST save — it cannot be retrieved later. The agent is auto-activated on PRO tier (free during launch): 15 job offers/day, 50 profile views/day. Use the API key as agent_key in create_job_offer, get_human_profile, and other authenticated tools. Typical first step before hiring.

Search for verified local service providers across 9 trade categories including floor coating, radon mitigation, foundation repair, basement waterproofing, crawl space repair, mold/asbestos remediation, septic services, commercial electrical, and laundry services. Returns provider name, rating, services offered, certifications, years in business, and a link to the full profile with contact details. Covers major US metro areas. Use list_niches first to get valid niche IDs, and list_service_types for valid service_type values.

Browse and compare Licium's agents and tools. Use this when you want to SEE what's available before executing. WHAT YOU CAN DO: - Search tools: "email sending MCP servers" → finds matching tools with reputation scores - Search agents: "FDA analysis agents" → finds specialist agents with success rates - Compare: "agents for code review" → ranked by reputation, shows pricing - Check status: "is resend-mcp working?" → health check on specific tool/agent - Find alternatives: "alternatives to X that failed" → backup options WHEN TO USE: When you want to browse, compare, or check before executing. If you just want results, use licium instead.

Unlocks access to other MCP tools. All tools remain locked with a 'Session Not Initialized' error until this function is called. Returns essential rules for blockchain data interactions.

Get the list of legal document templates available for generation on the platform (e.g. NDA, employment agreement, stock purchase agreement). For corporate services like 83(b) filing or registered agent, use get_available_corporate_services instead.

Get detailed information about board games on BoardGameGeek (BGG) including description, mechanics, categories, player count, playtime, complexity, and ratings. Use this tool to deep dive into games found via other tools (e.g. after getting collection results or search results that only return basic info). Use 'name' for a single game lookup by name, 'id' for a single game lookup by BGG ID, or 'ids' to fetch multiple games at once (up to 20). Only provide one of these parameters.

Returns information about the supplier network: available destinations, experience categories, booking platforms, and protocol details. Call this before search_slots to understand what regions and activity types are available.

Find the highest-yielding DeFi opportunities across Aave, Compound, Curve, Yearn, Morpho, and 100+ protocols. Returns APY, TVL, risk rating, and protocol audit status. Use this tool when: - A DeFi agent is allocating capital and wants to find the best risk-adjusted yield - You need to compare yield opportunities across multiple chains and protocols - An agent is rebalancing a yield portfolio and needs current APY data - You want to identify high APY opportunities with associated protocol risk ratings Returns per opportunity: protocol, asset, chain, apy, tvl_usd, apy_type (LENDING/LP/STAKING/VAULT), risk_rating (LOW/MEDIUM/HIGH), audited, reward_token. Example: getDefiYields({ chain: "ethereum", minApy: 8 }) → Aave USDC 9.2% (LOW risk, $2.1B TVL), Morpho DAI 11.4% (MEDIUM risk). Cost: $0.005 USDC per call.

Search the ENS knowledge base — governance proposals, protocol documentation, developer insights, blog posts, forum discussions, and Farcaster casts from key ENS figures (Vitalik, Nick Johnson, etc.). Covers ENS governance and DAO proposals, protocol details (ENSv2, resolvers, subnames), community sentiment, historical decisions, and what specific people have said about a topic. Powered by semantic search over curated ENS sources. Do NOT use this for name valuations, market data, or availability checks — use the other tools for those.

Authenticate this MCP session with your BopMarket API key. Call this once before using cart, checkout, price watch, order, or listing tools. Read-only tools (search, get_product, batch_compare, get_categories) work without auth. Buyer keys: sk_buy_*. Seller keys: sk_sell_*.

Verify factual claims about current DeFi market conditions. Supports two modes: - Single claim: provide claim_type, value, operator (and protocol/chain/asset as needed). Returns one verification result. - Batch mode: provide a JSON-encoded array in 'claims'. Each element has the same fields (claim_type, value, operator, protocol, chain, asset). Returns all results in one response. If 'claims' is provided, single-claim parameters are ignored. Args: api_key: Your PreFlyte API key (required). claim_type: What you're checking. One of: "supply_rate" — current supply APY (%) "borrow_rate" — current borrow APY (%) "price" — current token price (USD) "gas" — current base fee (gwei) "utilization" — current pool utilization (%) value: The numeric value you believe to be true. operator: Comparison operator. One of: "above" — actual must be >= value "below" — actual must be <= value "around" — actual must be within 10% of value protocol: Required for supply_rate, borrow_rate, utilization. Use "aave-v3" or "compound-v3". chain: Chain name — "ethereum" or "arbitrum". Default "ethereum". asset: Required for supply_rate, borrow_rate, price, utilization. Use token symbol like "USDC", "WETH", etc. claims: JSON-encoded array of claim objects for batch verification. Each object contains: claim_type, value, operator, and optionally protocol, chain, asset. When provided, single-claim params are ignored. Returns: Single mode: Dictionary with status (TRUE/FALSE), actual_value, claimed_value, delta, delta_pct, data_timestamp, and summary. Batch mode: Dictionary with 'mode', 'results' array, 'summary' counts, and 'verified_at' timestamp. Examples: Single: verify_claim(api_key="...", claim_type="supply_rate", value=5.0, operator="above", protocol="aave-v3", asset="USDC") Batch: verify_claim(api_key="...", claims='[{"claim_type": "supply_rate", ...}, ...]')

Retrieves comprehensive weather data including current conditions, hourly, and daily forecasts. **Specific Data Available:** Temperature (Current, Feels Like, Max/Min, Heat Index), Wind (Speed, Gusts, Direction), Celestial Events (Sunrise/Sunset, Moon Phase), Precipitation (Type, Probability, Quantity/QPF), Atmospheric Conditions (UV Index, Humidity, Cloud Cover, Thunderstorm Probability), and Geocoded Location Address. **Location & Location Rules (CRITICAL):** The location for which weather data is requested is specified using the `location` field. This field is a 'oneof' structure, meaning you MUST provide a value for ONLY ONE of the three location sub-fields below to ensure an accurate weather data lookup. 1. Geographic Coordinates (lat_lng) * Use it when you are provided with exact lat/lng coordinates. * Example: {"location": {"lat_lng": {"latitude": 34.0522, "longitude": -118.2437}}} // Los Angeles 2. Place ID (place_id) * An unambiguous string identifier (Google Maps Place ID). * The place_id can be fetched from the search_places tool. * Example: {"location": {"place_id": "ChIJLU7jZClu5kcR4PcOOO6p3I0"}} // Eiffel Tower 3. Address String (address) * A free-form string that requires specificity for geocoding. * City & Region: Always include region/country (e.g., "London, UK", not "London"). * Street Address: Provide the full address (e.g., "1600 Pennsylvania Ave NW, Washington, DC"). * Postal/Zip Codes: MUST be accompanied by a country name (e.g., "90210, USA", NOT "90210"). * Example: {"location": {"address": "1600 Pennsylvania Ave NW, Washington, DC"}} **Usage Modes:** 1. **Current Weather:** Provide `location` only. Do not specify `date` and `hour`. 2. **Hourly Forecast:** Provide `location`, `date`, and `hour` (0-23). Use for specific times (e.g., "at 5 PM") or terms like "next few hours" or "later today". If the user specifies minute, round down to the nearest hour. Hourly forecast beyond 120 hours from now is not supported. Historical hourly weather is supported up to 24 hours in the past. 3. **Daily Forecast:** Provide `location` and `date`. Do not specify `hour`. Use for general day requests (e.g., "weather for tomorrow", "weather on Friday", "weather on 12/25"). If today's date is not in the context, you should clarify it with the user. Daily forecast beyond 10 days including today is not supported. Historical weather is not supported. **Parameter Constraints:** * **Timezones:** All `date` and `hour` inputs must be relative to the **location's local time zone**, not the user's time zone. * **Date Format:** Inputs must be separated into `{year, month, day}` integers. * **Units:** Defaults to `METRIC`. Set `units_system` to `IMPERIAL` for Fahrenheit/Miles if the user implies US standards or explicitly requests it. * The grounded output must be attributed to the source using the information from the `attribution` field when available.

Modify an existing proposal part. For individual accountability/domain changes, use the children tools.

Set ENS resolver records for a name you own. Returns encoded transaction calldata ready to sign and broadcast. Supports address records (ETH, BTC, SOL, etc.), text records (avatar, description, url, social handles, AI agent metadata), content hash (IPFS/IPNS), ENSIP-25 agent-registration records, and ENSIP-26 agent context and endpoint discovery. Multiple records are batched into a single multicall transaction to save gas. Common text record keys: avatar, description, url, email, com.twitter, com.github, com.discord, ai.agent, ai.purpose, ai.capabilities, ai.category. ENSIP-25 support: Pass agentRegistration with registryAddress and agentId to automatically set the standardized agent-registration text record. This creates a verifiable on-chain binding between your ENS name and your agent identity in an ERC-8004 registry. ENSIP-26 support: Pass agentContext to set the agent-context text record (free-form agent description). Pass agentEndpoints with protocol URLs (mcp, a2a, oasf, web) to set agent-endpoint[protocol] discovery records. The returned transaction can be signed and submitted directly using any wallet framework (Coinbase AgentKit, ethers.js, etc.).

Retrieves comprehensive weather data including current conditions, hourly, and daily forecasts. **Specific Data Available:** Temperature (Current, Feels Like, Max/Min, Heat Index), Wind (Speed, Gusts, Direction), Celestial Events (Sunrise/Sunset, Moon Phase), Precipitation (Type, Probability, Quantity/QPF), Atmospheric Conditions (UV Index, Humidity, Cloud Cover, Thunderstorm Probability), and Geocoded Location Address. **Location & Location Rules (CRITICAL):** The location for which weather data is requested is specified using the `location` field. This field is a 'oneof' structure, meaning you MUST provide a value for ONLY ONE of the three location sub-fields below to ensure an accurate weather data lookup. 1. Geographic Coordinates (lat_lng) * Use it when you are provided with exact lat/lng coordinates. * Example: {"location": {"lat_lng": {"latitude": 34.0522, "longitude": -118.2437}}} // Los Angeles 2. Place ID (place_id) * An unambiguous string identifier (Google Maps Place ID). * The place_id can be fetched from the search_places tool. * Example: {"location": {"place_id": "ChIJLU7jZClu5kcR4PcOOO6p3I0"}} // Eiffel Tower 3. Address String (address) * A free-form string that requires specificity for geocoding. * City & Region: Always include region/country (e.g., "London, UK", not "London"). * Street Address: Provide the full address (e.g., "1600 Pennsylvania Ave NW, Washington, DC"). * Postal/Zip Codes: MUST be accompanied by a country name (e.g., "90210, USA", NOT "90210"). * Example: {"location": {"address": "1600 Pennsylvania Ave NW, Washington, DC"}} **Usage Modes:** 1. **Current Weather:** Provide `location` only. Do not specify `date` and `hour`. 2. **Hourly Forecast:** Provide `location`, `date`, and `hour` (0-23). Use for specific times (e.g., "at 5 PM") or terms like "next few hours" or "later today". If the user specifies minute, round down to the nearest hour. Hourly forecast beyond 120 hours from now is not supported. Historical hourly weather is supported up to 24 hours in the past. 3. **Daily Forecast:** Provide `location` and `date`. Do not specify `hour`. Use for general day requests (e.g., "weather for tomorrow", "weather on Friday", "weather on 12/25"). If today's date is not in the context, you should clarify it with the user. Daily forecast beyond 10 days including today is not supported. Historical weather is not supported. **Parameter Constraints:** * **Timezones:** All `date` and `hour` inputs must be relative to the **location's local time zone**, not the user's time zone. * **Date Format:** Inputs must be separated into `{year, month, day}` integers. * **Units:** Defaults to `METRIC`. Set `units_system` to `IMPERIAL` for Fahrenheit/Miles if the user implies US standards or explicitly requests it. * The grounded output must be attributed to the source using the information from the `attribution` field when available.

Browse and compare Licium's agents and tools. Use this when you want to SEE what's available before executing. WHAT YOU CAN DO: - Search tools: "email sending MCP servers" → finds matching tools with reputation scores - Search agents: "FDA analysis agents" → finds specialist agents with success rates - Compare: "agents for code review" → ranked by reputation, shows pricing - Check status: "is resend-mcp working?" → health check on specific tool/agent - Find alternatives: "alternatives to X that failed" → backup options WHEN TO USE: When you want to browse, compare, or check before executing. If you just want results, use licium instead.

Gets the status of a long-running operation. ***Usage*** Some tools (for example, `run_stream`) return a long-running operation. You can use this tool to get the status of the operation. It can be called repeatedly until the operation is complete. **Parameters** * `name`: The name of the operation to get. * `name` should be the name returned by the tool that initiated the operation. * `name` should be in the format of: `projects/{project}/locations/{location}/operations/{operation}`. **Returns** * An `Operation` object that contains the status of the operation. * If the operation is not complete, the response will be empty. Do not check more than every ten seconds. * If the operation is complete, the response will contain either: * A `response` field that contains the result of the operation and indicates that it was successful. * A `error` field that indicates any errors that occurred during the operation.

Returns information about the supplier network: available destinations, experience categories, booking platforms, and protocol details. Call this before search_slots to understand what regions and activity types are available.

Returns information about the supplier network: available destinations, experience categories, booking platforms, and protocol details. Call this before search_slots to understand what regions and activity types are available.

Find the nearest Met Office weather observation station to a UK location. Returns the station's geohash identifier, area name, region, and country. Use the returned geohash with the observations tool to get actual measured weather data from that station.

Get a multi-day weather forecast for any Swiss location. Returns daily summaries with temperature, precipitation, and weather icons. This uses official MeteoSwiss Open Data — the same forecasts powering the MeteoSwiss app and website. Accepts: - Postal codes: "8001" (Zurich), "3000" (Bern), "1200" (Geneva) - Station abbreviations: "ZUE" (Zurich Fluntern), "BER" (Bern) - Place names: "Zurich", "Basel", "Lugano" Coverage: ~6000 Swiss locations (all postal codes + weather stations + mountain points). Forecast horizon: up to 9 days. Updated hourly.

Detect the geometry file format from a filename or URL. Returns the detected format name and whether it is currently supported. Use this to check format support before making a paid analysis call. No payment required. Privacy policy: https://caliper.fit/privacy

Gets the latest status of a long-running operation. Several tools like `create_environment`, `delete_environments`, and `manage_pypi_packages` return an operation object, because they initiate processes that take time to complete. Use this tool to check if such an operation has finished and whether it was successful. Provide the `name` of the operation as returned by the tool that initiated it. A completed operation may include the details specific to the operation, described in the description of the tool that initiates the operation.

List all available news categories with their recap timeframes. Returns category codes that can be used with get_latest_news, get_news_recap, and other tools. Each category includes its code, display name, and how frequently recaps are generated.

List CVEs that ContrastAPI indexed from MITRE/GHSA BEFORE NVD has published them. These are early-warning vulnerabilities — we have the data, NVD doesn't yet. Use this to find the freshest, most actionable CVEs that other tools miss. Returns the same format as cve_search: count, total, truncated, offset, results array. Each result includes sources and first_seen_source fields showing which upstream (mitre/ghsa) first reported it.

Verify that a transaction targets a known, verified contract — not an arbitrary address. Cross-references against Etherscan (verified source code), Sourcify (independent verification), and Syenite's curated protocol registry. Use this to confirm a contract's identity before signing any transaction. Works for any transaction, not just Syenite's.

Report a bug, missing feature, UX friction, or documentation issue. Call this proactively when you encounter errors using Roboflow tools, when the user expresses frustration, when a tool is missing for the task at hand, or when a parameter is poorly documented. Returns confirmation that the feedback was recorded.

<tool_description> Search for products in the Nexbid marketplace. Alias for nexbid_search with content_type='product'. </tool_description> <when_to_use> When an agent needs to discover products (not recipes or services). Convenience alias — delegates to nexbid_search internally. </when_to_use> <combination_hints> list_products → get_product for details → create_media_buy for advertising. For recipes/services use nexbid_search with content_type filter. </combination_hints> <output_format> Product list with name, price, availability, score, and link. </output_format>

Submit a support request to the Skala team on behalf of the user. Call this when the user needs human assistance that AI cannot provide, the question is too complex or high-risk, or the user explicitly asks for human support. IMPORTANT: Always confirm with the user before calling — describe what you will submit and ask for their approval. Before calling, compile the issue from conversation context into the description.

Generate unsigned transaction calldata to withdraw a supplied asset from a lending protocol. Use max amount or specify the exact amount. Check lending.position.monitor first to ensure safe withdrawal.

FREE — Discover which Apollo tools match your task. Returns recommended tools by category with example calls. No payment required.

Search for airports and cities to get their identifiers for Google Flights tools. Returns: - IATA airport codes (e.g., 'JFK') for specific airports - kgmid (e.g., '/m/02_286') for cities - searches all airports in that city Use this tool when you have a city name like 'New York' or 'Paris' and need to convert it to codes that the flight tools accept. Note: Common IATA codes like JFK, LAX, SFO, LHR, CDG, NRT can be used directly without this tool.