"General greeting or query" matching MCP tools:

• get_cost_estimate

  mental-health-care

  Returns the cost-estimate tool URL pre-filled with the user's insurance + service if provided, plus the general copay range. The tool URL is a hand-off — the user verifies their plan there for an exact copay.

  Connector

• baselight_sdk_query_execute

  Baselight

  Execute a SQL query on Baselight and wait for results (up to 1 minute). The query executes and returns the first 100 rows upon completion, or info about a pending query that needs more time. Use DuckDB syntax only, table format "@username.dataset.table" (double-quoted), SELECT queries only (no DDL/DML), no semicolon terminators, use LIMIT not TOP. If query is still PENDING, use `sdk-get-results` to continue polling. If totalResults > returned rows, use `sdk-get-results` with offset to paginate.

  Connector

• kapruka_list_delivery_cities

  Kapruka MCP

  List or search Sri Lankan cities Kapruka delivers to. Use the `query` param to filter (e.g. "colombo" → all Colombo zones, "anur" → Anuradhapura). Without a query you get the first 25 cities alphabetically, which is rarely what an agent needs — pass a query. Returns canonical city names (use these as the `city` argument to kapruka_check_delivery) plus any common aliases / vernacular spellings. Args: params (ListDeliveryCitiesInput): - query (Optional[str]): Partial match filter - limit (int): Max results, 1–50 (default 25) - response_format (str): 'markdown' (default) or 'json' Returns: str: Cities list in the requested format. JSON schema: { "cities": [{"name": str, "aliases": [str]}], "total_matched": int, "showing": int }

  Connector

• search_notes

  anamnese

  Search notes by keyword or list recent notes. Returns summaries (id + description) only. Use get_note to retrieve the full content of a specific note. With query: Case-insensitive keyword search on description and content. Without query: Returns most recently updated notes.

  Connector

• search_solutions

  Civis

  Semantic search across the Civis knowledge base of agent build logs. Returns the most relevant solutions for a given problem or query. Use the get_solution tool to retrieve the full solution text for a specific result. Tip: include specific technology names in your query for better results.

  Connector

• search_products

  agentic-shelf

  Search products in the connected store by keyword. Use this when a shopper's query suggests specific terms the agent can match against product titles or tags — e.g. "HEPA air purifier" or "leather wristwatch". Matches Shopify's native storefront search behavior, so results align with what customers would find on the site. Args: query: Keyword or phrase to match. limit: Max products to return (1-50, default 10). Returns: Same shape as ``list_products``. Empty products list when no matches.

  Connector

• forum_create_topic

  argo-mcp

  Create a new forum topic (bug report, feature request, or general discussion). Always call forum_search first to check for duplicates. Call forum_list_categories to get the correct categoryId.

  Connector

• search_blog

  self-hosted-ai

  Search the Sovereign AI Blog for articles matching a natural language query, optionally filtered by tag and sorted by relevance or date. Behaviour matrix: - query='', sort=* -> list newest-first, optionally tag-filtered - query!='', sort=relevance -> TF-IDF ranked, optionally tag-filtered - query!='', sort=date_desc -> TF-IDF filtered (score > 0.001), then sorted by date Pure read-only, deterministic for a given KB snapshot.

  Connector

• search_products

  TrustRails

  HOW TO CALL THIS TOOL — read before every call: Decompose the user's request into filters first. Only what's left over goes in query. STEP 1: brand name → brand filter. STEP 2: product category → category filter. STEP 3: price → min_price/max_price. STEP 4: what remains → query. BAD: query='Sony headphones under £200' | GOOD: brand='Sony', category='Headphones', max_price=200, no query. BAD: query='tablet' | GOOD: category='Tablets', no query. BAD: query='smartwatch' | GOOD: category='Wearables', no query. BAD: query='macbook neo' | GOOD: brand='Apple', category='Laptops', query='neo'. BAD: query='Samsung QLED TV' | GOOD: brand='Samsung', category='TVs', query='qled'. If brand+category alone cover what the user wants, omit query entirely. Only put differentiating terms in query: model lines (neo, ultra, oled), variants, model numbers (WH-1000XM5, s25 ultra). CROSS-CATEGORY NOTE: Gaming headsets → category='Headphones', query='gaming headset'. The Gaming category is consoles/controllers/accessories only. Always set lite=true. If 0 results, broaden the query or drop filters. Use get_product for full specs. Search 26,000+ deduplicated UK electronics products across multiple retailers with price comparison. Covers: Laptops, Desktops, Phones, Tablets, Headphones, Monitors, TVs, Cameras, Keyboards, Mice, Speakers, Gaming, Wearables, Printers, Networking, Storage, Audio, Drones, Cables & Chargers. All prices in GBP. Returns summary data: title, brand, price, availability, category, purchase link, offer_count. When offer_count > 1, call get_product for all retailer offers. For spec-based queries (RAM, ports, screen size, weight etc.), search first then call get_product on top 3-5 results — do not assume specs from titles. STOCK: When availability is out_of_stock, mention it as an alternative and suggest checking back — do not silently omit it.

  Connector

• t54_list_operations

  Agentic Swarm Marketplace (T54 x402 MCP)

  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.

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol) Args: query: The search term - token symbol, name, or address. DO NOT include chain name here! result_type: Type filter - "token", "entity", "eoa", or "any" max_results: Maximum number of results (default: 25, max: 25) chain: Optional chain filter to narrow down token results to specific blockchain. If not further specified, leave it as None. If a chain is specified, ALWAYS use this parameter instead of adding chain name to the query string. Valid values: "ethereum", "solana", "base", "bnb", "polygon", "arbitrum", "avalanche", "optimism", etc. How to choose result_type: - token: Use when searching for a token by name, symbol, or contract address. **CRITICAL**: Use the `chain` parameter to filter by blockchain, NOT the query string! ✅ CORRECT: query="AAVE", chain="base" ❌ WRONG: query="AAVE base", chain=None - entity: Use when you want entity info by name/label (exchanges, funds, etc.) - eoa: Use when you have an address and need its labels or you have an ENS/SNS domain and need the resolved address - any: Mixed results (tokens/entities). Also auto-resolves ENS/SNS domains and, if token/entity results are empty and the query looks like an address, falls back to EOA labels. Important: - This is the only tool that can resolve domains. If you start from a domain, pass the Resolved Address to other tools. - **DOMAINS**: Strings ending in `.eth` (ENS) or `.sol` (SNS) are DOMAIN NAMES, not tokens. Use result_type="eoa" or "any" to resolve them. Examples: "vitalik.eth", "abracadabra.sol", "y22.eth" are domains that resolve to addresses. - **DO NOT** ASSUME that token is a NFT, always verify the name by using this tool first. - **DO NOT** add keyword `token` or chain names to the query string, unless this is explicitly in the token name or symbol! - **Focus** on **popular chains** like ethereum, solana, base and bnb when no chain is specified and the same token is deployed on multiple chains. - **If a chain is specified**, use the `chain` parameter to filter tokens by blockchain instead of including chain in query. - **DO NOT** rely on this endpoint for LATEST prices as this is delayed. Use `token_ohlcv` for latest prices.

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol) Args: query: The search term - token symbol, name, or address. DO NOT include chain name here! result_type: Type filter - "token", "entity", "eoa", or "any" max_results: Maximum number of results (default: 25, max: 25) chain: Optional chain filter to narrow down token results to specific blockchain. If not further specified, leave it as None. If a chain is specified, ALWAYS use this parameter instead of adding chain name to the query string. Valid values: "ethereum", "solana", "base", "bnb", "polygon", "arbitrum", "avalanche", "optimism", etc. How to choose result_type: - token: Use when searching for a token by name, symbol, or contract address. **CRITICAL**: Use the `chain` parameter to filter by blockchain, NOT the query string! ✅ CORRECT: query="AAVE", chain="base" ❌ WRONG: query="AAVE base", chain=None - entity: Use when you want entity info by name/label (exchanges, funds, etc.) - eoa: Use when you have an address and need its labels or you have an ENS/SNS domain and need the resolved address - any: Mixed results (tokens/entities). Also auto-resolves ENS/SNS domains and, if token/entity results are empty and the query looks like an address, falls back to EOA labels. Important: - This is the only tool that can resolve domains. If you start from a domain, pass the Resolved Address to other tools. - **DOMAINS**: Strings ending in `.eth` (ENS) or `.sol` (SNS) are DOMAIN NAMES, not tokens. Use result_type="eoa" or "any" to resolve them. Examples: "vitalik.eth", "abracadabra.sol", "y22.eth" are domains that resolve to addresses. - **DO NOT** ASSUME that token is a NFT, always verify the name by using this tool first. - **DO NOT** add keyword `token` or chain names to the query string, unless this is explicitly in the token name or symbol! - **Focus** on **popular chains** like ethereum, solana, base and bnb when no chain is specified and the same token is deployed on multiple chains. - **If a chain is specified**, use the `chain` parameter to filter tokens by blockchain instead of including chain in query. - **DO NOT** rely on this endpoint for LATEST prices as this is delayed. Use `token_ohlcv` for latest prices.

  Connector

• search_natural_language

  connect

  DEFAULT search — find works by name, title, or any descriptive query. Handles partial matches and title variations. TRIGGER: Any mention of a work by name ("the blue painting," "Self-Portrait"), or finding something ("where's that piece I did last year"). Use this to resolve work_ids before calling get_work, update_work, get_upload_url, or any tool needing a work_id. For structured filters (status, date, medium), use search_works instead. YOU (the connected AI) translate the query. Pass the user's natural language as `query` (for title/medium text search) and optionally set structured filters you can infer: status, date_start, date_end, medium, series_name, current_location_type, sort_by, sort_direction. Examples: "sold paintings from the 90s" → query: "painting", status: "sold", date_start: 1990, date_end: 1999. "the blue one" → query: "blue". "Self-Portrait" → query: "Self-Portrait".

  Connector

• perspective_list

  Perspective AI

  Lists perspectives — either browsing one workspace or searching by title across every workspace the user can access. Items include perspective_id, title, status, conversation count, and workspace info. Behavior: - Read-only. - Browse mode (workspace_id, no query): lists every perspective in that workspace. - Search mode (query): matches against the perspective title across accessible workspaces. Optional workspace_id narrows the search. Query must be non-empty and ≤200 chars. - Errors with "Please provide workspace_id to list perspectives or query to search." if neither is given. - Pass nextCursor back as cursor; has_more indicates further results. When to use this tool: - Resolving a perspective_id from a name the user mentioned (search mode). - Browsing a workspace's perspectives to pick or summarize. When NOT to use this tool: - Inspecting one known perspective in detail — use perspective_get. - Aggregate counts or rates — use perspective_get_stats. - Fetching conversation data — use perspective_list_conversations or perspective_get_conversations. Examples: - List all in a workspace: `{ workspace_id: "ws_..." }` - Search by name across all workspaces: `{ query: "welcome" }` - Search within a workspace: `{ query: "welcome", workspace_id: "ws_..." }`

  Connector

• search_authorities

  What Do They Know?

  Search WhatDoTheyKnow public authorities by name. Returns up to `limit` authorities whose name or short_name contains `query` (case-insensitive). Use the `slug` field with authority_json or build_request_url as the next step. Example: search_authorities("Liverpool") → slug "liverpool_city_council" Then: authority_json with that slug, or build_request_url with it.

  Connector

• query-docs

  xpay✦ DevTools Collection

  Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.

  Connector

• resolve_error

  DepScope

  Map error OR free-text query to a verified fix. USE WHEN: user pastes a concrete error/stack (ENOENT, ImportError, build failure) — pass `error`. OR user describes a symptom ('webpack slow', 'pip stuck') — pass `query`. Always prefer this over guessing a fix. RETURNS: exact-match {status, solution, confidence, source_url} or search results [{title, summary, source_url}].

  Connector

• mental-health-get-test

  Well-Being Check

  Loads one supported self-assessment into the widget by slug. Use `gad7` for anxiety screening, `phq9` for depression screening, and `who5` for general well-being screening when the user wants to take one of those assessments.

  Connector

• search_products

  Graffeo Coffee Roasting

  Search products in the connected store by keyword. Use this when a shopper's query suggests specific terms the agent can match against product titles or tags — e.g. "HEPA air purifier" or "leather wristwatch". Matches Shopify's native storefront search behavior, so results align with what customers would find on the site. Args: query: Keyword or phrase to match. limit: Max products to return (1-50, default 10). Returns: Same shape as ``list_products``. Empty products list when no matches.

  Connector

• search_data

  Opendata Koumoul

  Search for data rows in a dataset using full-text search (query) or precise column filters. Returns matching rows and a filtered view URL. Use to retrieve individual rows. Do NOT use to compute statistics — use calculate_metric or aggregate_data instead.

  Connector