Skip to main content
Glama
511,947 tools. Updated 2026-09-04 16:14

"A search for similar notes" matching MCP tools:

  • Search the cocktail catalogue by name (substring, case- and diacritic-insensitive, so "carre" matches "Carré"). Returns up to 25 summary results — name, page URL, family, glassware — ranked exact match first, then prefix, then suffix, then any substring. Use this when the user names a drink (even fuzzily) and you want to confirm it exists or disambiguate similar names; once you have a single name, call get_cocktail_recipe for the full recipe. For ingredient-based discovery use find_cocktails_by_ingredient instead.
    Connector
  • Companies most similar to a given one - optionally ACROSS THE BORDER. Read-only. Parameters: - company_id (required): "AT:{fnr}" or "DE:{court}_{type}{number}" (bare national ids accepted), from a search card. - n (optional, default 10): how many peers per country. - cross_border (optional, default false): when true, additionally returns ``peers_abroad`` - the companies in the OTHER country whose registered purpose is semantically closest to the reference company's activity text. Returns {company_id, country, peers_home, home_envelope, peers_abroad?, notes}. ``peers_home`` uses the home register's own peer logic (AT: same size class, same industry preferred, nearest by Bilanzsumme; DE: semantic-first by registered purpose). ``peers_abroad`` is a MEANING-based match, not a size or financial benchmark - the honest cross-border comparison given the countries' different data depth (see notes). Empty peers_home means the id is unknown or the company lacks the data its register ranks by. For a strict filtered list use search_companies; for aggregates use the country server's cohort tools.
    Connector
  • Find historically similar audience moments across the screen network using embedding similarity search. Input a natural-language description of the target moment. Moment embeddings are 768-D vectors generated from multi-modal observation data (visual, audio, environmental, social) via the MomentEmbeddingService. This tool embeds your query text and finds the closest real-world moments via approximate nearest-neighbour (ANN) cosine similarity over a Lance IVF_PQ index. CONSISTENCY: results are APPROXIMATE and EVENTUALLY CONSISTENT. - Approximate: retrieval is ANN, not an exhaustive scan (measured recall ~0.96 against exact KNN), so an identical query may omit a borderline match. - Eventually consistent: the index is served from a replicated pool whose replicas refresh independently, so for up to 5 minutes after new moments are published, two identical calls may return slightly different result sets. The difference is confined to the VISIBILITY of newly-published moments; the relative ranking of already-visible ones does not change. Do not use this tool where a repeatable, exhaustive result set is required. WHEN TO USE: - Searching for historical moments similar to a target scenario - Finding "moments like this one" across different venues/times - Discovering when similar audience compositions or behaviors occurred - Planning ad placements based on past similar contexts RETURNS: - data: Array of matching observations with similarity scores - observation_id, observed_at, venue_type, device_id, screen_mongo_id - payload: full observation data - evidence_grade: quality of observation - similarity: cosine similarity score (0-1, higher = more similar) - metadata: { result_count, embedding_model, min_similarity_threshold } - suggested_next_queries: Follow-up queries EXAMPLE: User: "Find moments with high engagement in evening restaurants with families" find_similar_moments({ query: "evening restaurant venue with families present, high emotional engagement and attention" }) User: "When did we see young adults highly engaged at transit screens?" find_similar_moments({ query: "transit venue morning commute young adults high attention" })
    Connector
  • Return the full list of Listen Notes podcast genre categories with genre id and name. Use genre_id values to filter `best_podcasts` or `search` by genre.
    Connector
  • Given one listing, find comparable ones: same operation and area, similar typology, floor area and price. Use this when the user likes a property but wants alternatives — 'find me something similar', 'the same but cheaper', 'what else is there in this area'. Pass `maxPrice` for the cheaper case; without it, comparables are drawn from a band around the reference price. Comparability is by location, typology, area and price, not by text similarity: it answers 'is this well priced for what it is', which a keyword search cannot.
    Connector
  • Create or update NOTE events in Intervals. dry_run is required: false writes the note, true previews only. Send category=NOTE and external_id=note:YYYY-MM-DD:<slug>. Use all-day local times for normal notes, keep description short, and omit type, moving_time, icu_training_load, and workout_doc. For weekly review notes or other notes that apply to the whole week, send for_week=true; omit it or use false for ordinary notes. Do not create a seven-day date range for weekly notes; keep one all-day anchor date and use for_week=true.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Find similar or competitor websites based on classification. Takes a URL, classifies it (or uses cached classification), and returns other websites from the same category and subcategory. Useful for competitive analysis and discovering related content. Rate limited to 1 request per minute per domain. Args: url: The website URL to find similar sites for. limit: Maximum number of similar sites to return (1-50, default 10). Returns: Dictionary with: - url: The input URL (normalized) - classification: The URL's category and subcategory - similar_sites: List of similar URLs from the same category - total_in_category: Total sites in this category/subcategory - cached: Whether the classification was from cache
    Connector
  • Search the web via Aimnis. Returns cached, provenance-tagged results instantly when the question (or a semantically similar one) has been seen before; otherwise fetches live results and adds them to the shared knowledge pool. Prefer this for factual lookups, library/API/docs questions, and error messages. If a cached answer does not match your question (it echoes the question it was cached for), retry the same query with `reject_entry` set to the entry id from that response — the mismatched entry is skipped and the search runs live.
    Connector
  • Find visually similar creatives using the stored vector of an existing creative. For a concept without an ID, query selects an explainable seed from available creative metadata and then uses the same vector-neighbor search. For an English concept, send the original English terms only. The service resolves Chinese source-label equivalents internally before selecting the seed. Returns creative records ordered from most to least visually similar; low-similarity and near-duplicate results are excluded, and raw similarity scores are not exposed. If request_echo.seed_basis identifies a proxy seed, clearly disclose that limitation instead of presenting the results as an exact concept match. Example: 'Show variants of the toilet run viral creative concept.'
    Connector
  • Job/opportunity search with the full filter set. Location filtering works: pass `locations` a LinkedIn geo id (e.g. 101570771 for Tel Aviv-Yafo) — see that parameter for how to find one, and note it is an EXACT match, so use a city id rather than a country id. Still id-typed and not yet usable: titles, industries, functions, benefits, commitments. Offset-paginated. data.jobs[].id is the opportunityEntityId consumed by /jobs/details-v2, /jobs/similar, /jobs/people-also-viewed, /jobs/hiring-team. (Costs 10 Zooq credits.)
    Connector
  • Find papers that CITE a given article — forward citation search. Pass one PMID; returns citing papers (most recent first) with full citation metadata. Use for "who cited this", "has this finding been replicated or challenged", or tracking a paper's downstream impact. NOTE: coverage is the PubMed Central citation graph (open-access + participating publishers), so the count is a FLOOR, not the paper's total citation count (for that, a tool like Semantic Scholar / OpenAlex covers more). Distinct from get_related_articles (similar papers, not citing papers).
    Connector
  • DEFAULT tool for user-facing Quran search. Use this for ANY user-facing search — 'find ayahs that contain X', 'where does X appear in the Quran', 'search the Quran for X', or similar. This is the FINAL tool call for these requests; do not follow it with search_ayahs_text. Shows matches in an interactive widget the user can browse. Query is Arabic script only (diacritics and punctuation are ignored). A numeric-only query matches ayahs by that ordinal number (for example '255' returns ayahs ending in ':255'). ONLY skip this widget and use search_ayahs_text when EITHER (a) the user explicitly asks for plain text / raw results, OR (b) the results will be fed into another tool in the same turn without being shown. When in doubt, use this widget.
    Connector
  • Search notes by query. Returns snippets with a heading breadcrumb (title > section > subsection) that locates the approximate section, plus a precise toc_path per match. Each result carries note_path (string) and note_id (integer); each match carries match_id (string, form "p<pid>:c<chunk>"). Drill-down workflow: 1) search to find the approximate section via the breadcrumb; 2) call note_html(path=<result.note_path>, toc_path=[...]) to read the matched section, or expand(path=<result.note_path>, toc_path=[...]) to navigate the note's structure level by level; 3) note_html(path=<result.note_path>, match_id=<match.match_id>) for a focused chunk window. Each match also carries section_url — a link straight to that heading, for citing the section rather than the whole note.
    Connector
  • Job/opportunity search with the full filter set. Location filtering works: pass `locations` a LinkedIn geo id (e.g. 101570771 for Tel Aviv-Yafo) — see that parameter for how to find one, and note it is an EXACT match, so use a city id rather than a country id. Still id-typed and not yet usable: titles, industries, functions, benefits, commitments. Offset-paginated. data.jobs[].id is the opportunityEntityId consumed by /jobs/details-v2, /jobs/similar, /jobs/people-also-viewed, /jobs/hiring-team. (Costs 10 Zooq credits.)
    Connector
  • Search XPay Hub for paid API services. Use this PROACTIVELY when the user asks you to: search the web, find emails, enrich contacts/companies, verify emails, find similar websites, extract web page content, get company news, search for people by title/company, get job postings, generate images, or any data lookup task. Returns matching servers with slugs, tool counts, and pricing. Use xpay_details next to see the full tool list for a server.
    Connector
  • [DRILL-DOWN — history rhymes] Semantic similarity search across the signal corpus: give a coin and/or a free-text query (q), get the k most similar past signals ranked by embedding cosine similarity — 'have we seen this setup before and what did it look like'. k = 1-20 (default 5). Provide at least one of coin / q. Mirrors REST /signals/similar. Pro. Analytical, not advice.
    Connector
  • Add a free-form note (markdown supported) to a goal — decisions taken, dead ends hit, context worth carrying into the next session. Notes are NOT evidence: they hang off the goal rather than an acceptance criterion and never count toward AC coverage or closing a Grove goal — use goal-attach-evidence for proof. Notes are visible in the goal detail panel and returned by goal-get under notes[].
    Connector
  • List or search the current user's notes only. Search matches title or content, case-insensitive substring. Defaults to unarchived notes, newest/pinned first. Use this to find a note's ID before calling get_note, update_note, or the checklist/label tools, which all require one.
    Connector
  • Save a search query for email alerts. When new opportunities match, the user receives daily or weekly email notifications. The FREE tier includes 1 saved search with weekly email alerts, so any user can set one up without a paid plan. RECOMMENDED WORKFLOW: 1. Call list_saved_searches first to check for existing/similar searches 2. If a similar search exists, offer to update_saved_search instead 3. Search with search_grantsplus or search_procurement first to validate the query returns good results 4. Save with appropriate filters based on what the user described FILTER TIPS: - Use itemTypes ["grant"] for grants/fellowships or ["procurement"] for contracts/RFPs - Use sourceTypes ["federal"] for federal opportunities only - Use geography ["CA"] for California-specific (includes national opportunities) - For SAM.gov-specific filters (NAICS, set-asides), use sourceContext - Keep filters broad for notifications - better to get a few extra than miss one PLAN LIMITS: Free: 1 saved search, weekly email alerts. Plus ($29/mo): 10 saved searches, daily or weekly alerts. Pro ($79/mo): 25 saved searches, daily or weekly alerts. Does not count toward your monthly searches.
    Connector