Skip to main content
Glama
133,525 tools. Last updated 2026-05-25 17:48

"General search" matching MCP tools:

  • 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
  • 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
  • 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
  • [tourradar] Search for tours by title using AI-powered semantic search. Returns a list of matching tour IDs and titles. Use this when you need to look up a tour by name. When you know tour id, use b2b-tour-details tool to display details about specific tour
    Connector
  • 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
  • [tourradar] Search tour reviews using AI-powered semantic search. Requires tourIds to scope results to specific tours. Use this when the user asks about reviews, feedback, or experiences for specific tours. Combine with an optional text query to find reviews mentioning specific topics (e.g., 'food', 'guide', 'accommodation'). When you don't have tour IDs, use vertex-tour-search or vertex-tour-title-search first to find them.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Brave Search MCP — independent web index (no Google/Bing dependency)

  • 4 web-search tiers (x402 USDC on Base) - simple/medium/deep/cached. Free health.

  • 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
  • Returns general information about the Makuri platform, including mission, target users, founding details, and company information. Use this tool when the user asks 'what is Makuri', 'who made it', or wants a general overview.
    Connector
  • Send a message to Atlas Advisor for lightweight hiring advice (2 credits). Faster and cheaper than atlas_chat, no tool use -- best for general hiring questions. Returns AI response text and a conversation_id. Omit conversation_id to start a new conversation; include it to continue a thread.
    Connector
  • Quick AI visibility scan. Returns three scores: AEO Score (0-100, AI search engine findability), GEO Score (0-100, AI citation readiness), and Agent Readiness Score (0-100, AI agent interaction capability). Also returns AI Identity Card with mention readiness (0-100, predicts how likely AI will mention the brand), detected competitors, business profile (commerce/saas/media/general), and top 5 issues. 67+ checks across 12 categories. Free — no API key needed. Does NOT return per-check details or fix code — use audit_site for full breakdown, fix_site for generated fixes, compare_sites to benchmark against a competitor.
    Connector
  • OpenAI ChatGPT Deep Research / Connectors search contract. Returns matching Dynamoi artists, campaigns, and Smart Links so they can be cited in a deep-research session. For regular ChatGPT chat use dynamoi_search instead.
    Connector
  • Use this when the user mentions a place, neighbourhood, landmark, or area but does not give exact coordinates. Examples: 'near the Louvre', 'in Trastevere', 'around Times Square', "walking distance from St Paul's Cathedral". Returns experiences matched first by exact venue/neighbourhood, then by city centre fallback. Do not use for general city-wide search; use search_experiences for that.
    Connector
  • Execute a search and return ranked Markdown results (title, URL, snippet). ## Two modes ### Mode 1 — General web search (no list_domains needed) Omit domain and sub_domain entirely. Use when the query is open-ended and does not target a specific structured data source. Example: search(query="what is quantum computing") ### Mode 2 — Vertical search (call list_domains first) Use when the query targets a specific domain: stocks, patents, flights, CVEs, weather, academic papers, etc. Steps: 1. Call list_domains to get the sub_domain and mandatory query format for the target domain. 2. Pass domain + sub_domain from list_domains output. Never guess them. 3. Format query exactly as specified in the query_format column — wrong format = wrong results. **IMPORTANT: For any query that may belong to a supported vertical domain, ALWAYS call list_domains first — vertical search produces significantly better results than general web search.** ## Decision rule — which mode to use Use Mode 2 (vertical) when ANY of these apply: - Query involves a ticker, DOI, CVE, IATA code, patent number, address, or other structured identifier - Query targets a specific vertical: finance, legal, academic, security, travel, geo, environment, etc. - User asks for real-time or specialized data (stock price, weather, flight status, drug info, etc.) Use Mode 1 (general) when the query is purely conversational or open-ended with no structured lookup. ## After getting results — when to call extract Search returns titles + snippets only. Call extract when: - The snippet is truncated or insufficient to answer the question - User asks to read, summarize, or get details from a specific URL - You need to verify a claim or fact from the source page - The answer requires data only visible in the page body (tables, sections not in snippet) ## Query decomposition One intent per search call. For 2–5 independent queries use batch_search instead. WRONG: search(query="AAPL price and earnings and analyst rating") RIGHT: batch_search(queries=[{query:"AAPL price",...}, {query:"AAPL earnings",...}])
    Connector
  • Searches Brave's Place Search API. A single call may populate any combination of `results` (POIs), `cities`, `addresses`, `streets`, and `location` (the resolved search area), depending on the query shape. Use for POIs near coordinates or a named area, browsing general POIs (omit `query`, supply coords or `location`), disambiguating bare city names, resolving specific addresses, or looking up streets. Anchor via `latitude`+`longitude` or `location`; with neither, `query` is required.
    Connector
  • Deploy an agent from a template (28 general + 9 vertical). Creates agent + skills + tools + grading suite in one shot. Use kopern_list_templates to see available slugs.
    Connector
  • [tourradar] Use this when you need to find city IDs for tour search filters like start city, end city, or cities to visit. Searches for cities by name within a specific country. Supports multiple name variants to handle different spellings (e.g., Krakow, Kraków, Cracow).
    Connector
  • Get closed/resolved support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). # fetch_closed_tickets ## When to use Get closed/resolved support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). ## Parameters to validate before calling - search (string, optional) — Search by subject or description (case-insensitive) - platform (string, optional) — Filter by platform: renaissance, api, general, overture, winners - priority (number, optional) — one of: 1, 2, 3 — Filter by priority: 1 (Low), 2 (Medium), 3 (High) - page (number, optional) — Page number for pagination (default: 1, 20 tickets per page)
    Connector
  • Get open support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). # fetch_open_tickets ## When to use Get open support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). ## Parameters to validate before calling - search (string, optional) — Search by subject or description (case-insensitive) - platform (string, optional) — Filter by platform: renaissance, api, general, overture, winners - priority (number, optional) — one of: 1, 2, 3 — Filter by priority: 1 (Low), 2 (Medium), 3 (High) - page (number, optional) — Page number for pagination (default: 1, 20 tickets per page)
    Connector
  • Book a handyman for general home repairs: furniture assembly, TV mounting, drywall patching, door fixes, minor plumbing fixtures, and similar non-specialist tasks. Returns a confirmed booking. Call /quote first.
    Connector
  • OpenAI deep-research / company-knowledge compatibility. Search Cyclesite's active UK used-bike listings by free-text query (matches title, brand, model). Returns the canonical OpenAI shape: { results: [{ id, title, url }] }. Use the id to call fetch() for the full document.
    Connector