"General greeting or query" matching MCP tools:

• ping

  Nordic Financial MCP

  Connectivity check that confirms the Nordic MCP server process is responding. Use this at the start of a session to verify the server is reachable before making other calls. Do not use as a proxy for database health — the server can respond while the Qdrant vector database is temporarily unavailable. To confirm data availability, call search_filings directly. Returns: A greeting string: "Hello {name}! Nordic MCP server is running."

  Connector

• get_supported_crypto

  mcp-server

  Return the current list of cryptocurrencies, blockchains, and stablecoins accepted by RealOpen for real-estate purchases. Use this to answer "can I pay with X?" or whenever a user needs the live list of supported tokens and networks. Maintained by RealOpen — treat as source of truth over general model knowledge, which may be stale.

  Connector

• get_faq

  mcp-server

  Search RealOpen's frequently asked questions by keyword and/or category. Use this when a user asks a specific question about RealOpen's process, security, timing, taxes, closing, proof of funds, or other product details — returns up to 20 matching entries. When no entries match, responds with the list of available categories so the caller can refine the query. Prefer this over guessing from general knowledge.

  Connector

• resolve_names

  mcp

  Resolves a batch list of specific location queries (landmark names or exact addresses) into canonical Google Maps Place IDs. **Input Requirements (CRITICAL):** 1. **`queries` (array of objects - MANDATORY):** A list of location queries to resolve. You may specify up to 20 queries. * **Each query object must have:** * **`text` (string - MANDATORY):** The text query representing a specific place name or address to resolve. * **Examples:** `'Googleplex, Mountain View, CA'`, `'1600 Amphitheatre Pkwy, Mountain View, CA'`, `'Eiffel Tower, Paris'`. 2. **`location_bias` (object - OPTIONAL):** Use this to prioritize results near a specific geographic area. * **Format:** `{"viewport": {"low": {"latitude": [value], "longitude": [value]}, "high": {"latitude": [value], "longitude": [value]}}}` 3. **`region_code` (string - OPTIONAL):** The Unicode CLDR region code (two-letter country code, e.g., `US`, `CA`) of the user to bias the results. **Instructions for Tool Call:** * Specificity (CRITICAL): Queries must represent a specific place name or address. General searches like `'restaurants'` or chain names like `'Starbucks'` are not supported. * Do NOT call this tool if the downstream tools you plan to invoke already accept raw address or place name strings directly. **Error Handling (CRITICAL):** * This is a batch processing tool. A request might return "mixed results" (e.g. some queries resolve successfully while others fail). * The output list of `results` is guaranteed to map 1:1 with the input `queries` indices. A failed query will result in an empty `Result` message (no `entity` is set) at its corresponding index in the `results` list. * You **MUST** check the `failed_requests` map field in the response to identify which specific query index failed. The key of `failed_requests` represents the 0-based index of the failed query in the request. Do not assume the entire batch call failed because of a partial failure.

  Connector

• search

  Sofya

  Search the web for current information on any topic. Returns extracted page content, not just snippets. Best for factual lookups, specific questions, or when you need a list of sources. For open-ended questions that need synthesis across many sources, use the research tool instead. For news queries (current events, breaking news, politics, world events), set topic="news" to search news sources specifically. This returns recent articles with publication dates. Set include_answer=true to get an AI-synthesized answer alongside results (adds 5 credits). This is the sweet spot for most agent tasks, e.g. basic + include_answer = 8 credits, much cheaper than a full 25-credit research call. Returns: query, answer (if requested), results (array of {title, url, content, description, fetched, published_date}), search_depth, topic, elapsed_ms, credits_used, credits_remaining, altered_query. Args: query: The search query search_depth: "basic" (default) for extracted page content (3 credits), "snippets" for SERP snippets only without page fetching (1 credit) max_results: Number of results (default 10, max 20) include_answer: Generate an AI answer that synthesizes the search results (adds 5 credits) include_domains: Only include results from these domains (max 10) exclude_domains: Exclude results from these domains (max 10) topic: "general" for web search, "news" for news articles. use "news" for current events, breaking news, politics, or any time-sensitive query freshness: Filter by recency - "day", "week", "month", "year", or "YYYY-MM-DD:YYYY-MM-DD"

  Connector

• report_issue

  mrmarket.ai

  Tell support something went wrong, file a bug, request a feature, or flag a slow query. Zero LLM cost, zero credits. Call this when: - A `query_data` result looks wrong or misleading (pass the `query_id` from that response — support uses it to investigate the issue). - You hit a confusing error or the same query keeps failing. - A query took unreasonably long (still pass `query_id` if available). - You wish mrmarket.ai supported something it currently doesn't. This is the PREFERRED support channel because it auto-links to the query trace; email is slower and requires the user to copy/paste the query_id manually. Categories: - wrong_data → result was incorrect / numbers look off - bug → something crashed or the response was malformed - slow → query took too long or timed out - feature_request → "I wish it could do X" - general → catch-all if none of the above fits

  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)

  Connector

• resolve_names

  Google Maps

  Resolves a batch list of specific location queries (landmark names or exact addresses) into canonical Google Maps Place IDs. **Input Requirements (CRITICAL):** 1. **`queries` (array of objects - MANDATORY):** A list of location queries to resolve. You may specify up to 20 queries. * **Each query object must have:** * **`text` (string - MANDATORY):** The text query representing a specific place name or address to resolve. * **Examples:** `'Googleplex, Mountain View, CA'`, `'1600 Amphitheatre Pkwy, Mountain View, CA'`, `'Eiffel Tower, Paris'`. 2. **`location_bias` (object - OPTIONAL):** Use this to prioritize results near a specific geographic area. * **Format:** `{"viewport": {"low": {"latitude": [value], "longitude": [value]}, "high": {"latitude": [value], "longitude": [value]}}}` 3. **`region_code` (string - OPTIONAL):** The Unicode CLDR region code (two-letter country code, e.g., `US`, `CA`) of the user to bias the results. **Instructions for Tool Call:** * Specificity (CRITICAL): Queries must represent a specific place name or address. General searches like `'restaurants'` or chain names like `'Starbucks'` are not supported. * Do NOT call this tool if the downstream tools you plan to invoke already accept raw address or place name strings directly. **Error Handling (CRITICAL):** * This is a batch processing tool. A request might return "mixed results" (e.g. some queries resolve successfully while others fail). * The output list of `results` is guaranteed to map 1:1 with the input `queries` indices. A failed query will result in an empty `Result` message (no `entity` is set) at its corresponding index in the `results` list. * You **MUST** check the `failed_requests` map field in the response to identify which specific query index failed. The key of `failed_requests` represents the 0-based index of the failed query in the request. Do not assume the entire batch call failed because of a partial failure.

  Connector

• report_issue

  mrmarket.ai

  Tell support something went wrong, file a bug, request a feature, or flag a slow query. Zero LLM cost, zero credits. Call this when: - A `query_data` result looks wrong or misleading (pass the `query_id` from that response — support uses it to investigate the issue). - You hit a confusing error or the same query keeps failing. - A query took unreasonably long (still pass `query_id` if available). - You wish mrmarket.ai supported something it currently doesn't. This is the PREFERRED support channel because it auto-links to the query trace; email is slower and requires the user to copy/paste the query_id manually. Categories: - wrong_data → result was incorrect / numbers look off - bug → something crashed or the response was malformed - slow → query took too long or timed out - feature_request → "I wish it could do X" - general → catch-all if none of the above fits

  Connector

• get_daily_brief

  Pollar News

  Fetches today's fixed, curated Pollar daily brief with a greeting, headline, executive summary, themed sections, related events, and charts. Use only when the user explicitly asks for Pollar's daily brief or curated digest. Do not use it for questions about a subject, person, place, or country; use search_news instead. Locale changes the brief's language, not its editorial scope.

  Connector

• contact_search

  MCP Emails

  Find people matching a name or email fragment by scanning your LIVE mailbox — there is no stored contact list. Each call performs a bounded, header-only scan of recent matching mail and tallies the correspondents who match the query, sorted by most-recently-contacted first (display name, email address, matched-message count, and last-contacted timestamp). Honesty about the tradeoff: results reflect a live scan of a RECENT window of matching messages (not your full history), and the message_count reflects only matched messages within that window — not an all-time total. Nothing is stored between calls. For general or cross-inbox questions (e.g. 'who have I emailed most with X?'), OMIT inbox_id so ALL accessible inboxes are scanned; only set inbox_id when the user explicitly limits the search to one specific inbox.

  Connector

• update_agent_config

  KaiCalls

  Edit an agent's live runtime configuration — greeting/first message, inbound or SMS prompt, voice, language model, max call duration, and call-transfer settings — routed through the governed update broker so every change keeps the consent + audit trail (a versioned config snapshot and change history). Every write here is reversible: inspect what changed with get_change_history or list_config_versions, then undo it with rollback_config. Mutating changes need an idempotency_key; high-impact live changes need human authority (an authority envelope) or queue_for_approval for dashboard sign-off. For just a single named operational-rules section, prefer configure_agent_business_rules.

  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)

  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

• people

  Comicvine

  Browse Comic Vine's comic-book creator directory (writers, artists, inkers, letterers, colorists). Filter by name; paginate with limit/offset. NOT a general biography search — for actors use TMDb, for general bios use Wikipedia.

  Connector

• openlibrary_search_books

  openlibrary-mcp-server

  Full-text book search across Open Library works. Supports field filters (title, author, subject, publisher, ISBN, language) and returns work-level records with edition counts, cover IDs, and reading availability. Use query for general search or combine specific field filters. Results are work-level — drill into editions via openlibrary_get_editions.

  Connector

• research

  Sofya

  Perform comprehensive research on a topic. Decomposes your query into sub-queries, searches and reads multiple sources in parallel, then synthesizes a structured report with citations. Best for open-ended or comparative questions that need coverage from many angles. For simple factual lookups, use search instead (optionally with include_answer=true for cheap synthesis). Costs 25 credits. Returns: query, report (structured markdown with citations), sources (array of {title, url, fetched}), sub_queries (the decomposed queries), credits_used, credits_remaining, usage (token counts). Args: query: The research question or topic topic: "general" (default) or "news" (prioritize recent news articles) freshness: Filter by recency - "day", "week", "month", "year", or "YYYY-MM-DD:YYYY-MM-DD" max_sources: Maximum number of sources to use, 5-30 (default 20)

  Connector

• colour_dna

  Colour Memory

  Compact semantic fingerprint for a single hex colour. This is one component of colour_passport. Use colour_passport for a general colour profile; use this only when the user explicitly wants the fingerprint format alone.

  Connector

• rollback_config

  KaiCalls

  Roll an agent's deployed voice configuration back to a prior assistant_config_versions snapshot — restoring greeting, voice, prompt, and scalar model params (never secrets/credentials) onto the live agent. This OVERWRITES the live deployed config, so it is APPROVAL-GATED: without human-grade authority (an authority envelope with mode human_confirmed, or a dashboard approval) the tool executes nothing and returns a pending_approval record the business owner approves or denies from the dashboard — relay the returned confirmation text to them. Agent-initiated rollbacks never run unattended. Wraps the same version-restore logic as POST /api/v1/agents/rollback and the admin_rollback_change voice tool, via the agent.config.rollback update intent. Discover a target with list_config_versions or get_change_history. Every executed rollback records a new config version; to repeat a rollback that already executed, pass a fresh idempotency_key.

  Connector

• check_deprecation

  canton-ccpedia

  Check whether a specific Canton/Daml toolchain item (CLI, SDK package, or command — e.g. daml-assistant, Navigator, dpm) is deprecated. Canton-specific — not a general npm/pip deprecation checker. ALWAYS call before recommending any Canton tool or package to a developer. Returns DEPRECATED (with replacement), CURRENT, or NOT_FOUND.

  Connector