Skip to main content
Glama
649,985 tools. Updated 2026-10-08 03:46

"A search for the term 'Prompt'" matching MCP tools:

  • Look up the 99 Names of Allah (Asma ul Husna). Returns Arabic, transliteration, English and Bengali. Give a number for one name, a search term to match by meaning or transliteration, or neither to get all 99.
    ConnectorNo auth
  • Keyword Research (marketplace term universe): search the FULL Top Search Terms store by phrase - not anchored to any ASIN. Filters: contains (up to 5 substrings, ANDed), department, rank_max, min_volume; period WEEK or MONTH (MONTH = monthly volumes); sort rank | volume | trend. Each term: search_frequency_rank, volume (amazon_sqp = TRUE Amazon volume where any account's SQP covers the term; estimated_from_rank with volume_band otherwise), rank_change vs ~4 periods back, and the top-3 clicked ASINs with click/conversion shares (the term's competitive landscape). The estimator block reports calibration health (pairs, typical error factor, band coverage). Use keyword_finder for ASIN-anchored lookups; this tool for term-first research. For the guided process start with keyword_opportunities.
    ConnectorOAuth
  • List the full eDiscovery Decoder MCP surface — every tool, prompt, and resource, plus the suggested demo flow and safety boundaries — with an example prompt for each. Call this first when you are unsure which tool fits the user's question, or when tool-search shows only a partial list.
    ConnectorNo auth
  • [DEPRECATED — renamed tag_rule_list. Will be removed after 2026-10-07.] List your org's TAGGING RULES (the dashboard's 'Tagging rules') — labels applied to posts your Watchers already ingest. NOT the dashboard's Keyword Monitor: for the keywords that search all of Reddit daily, use keyword_monitor_list. Each rule tags matching Dataset records whose title or body mentions its term as a whole word. Returns the term, active status, and match statistics. Changes take effect on the next scheduled processing cycle. Existing opportunity scores and matches are not retroactively updated. (requires a free Prowlo account — call it to get a signup link)
    ConnectorNo auth
  • List your org's TAGGING RULES (the dashboard's 'Tagging rules') — labels applied to posts your Watchers already ingest. NOT the dashboard's Keyword Monitor: for the keywords that search all of Reddit daily, use keyword_monitor_list. Each rule tags matching Dataset records whose title or body mentions its term as a whole word. Returns the term, active status, and match statistics. Changes take effect on the next scheduled processing cycle. Existing opportunity scores and matches are not retroactively updated. (requires a free Prowlo account — call it to get a signup link)
    ConnectorNo auth
  • Full-text search over the knowledge graph. Matching ignores accents and apostrophes, so query in the user's own words; every hit carries the fields it matched and a score. BM25 relevance: each query term is weighted by how RARE it is in this corpus and by where it hits (name 3, tags 2, questions 2, body 1). A hit must also cover a minimum share of the question's information, measured in the same rarity weights — matching only common words does not qualify. Centrality (how many objects point at this one) breaks TIES ONLY and is never part of the score, so it cannot make an irrelevant object rank. Two hits with the same matched_fields can still differ: the score is rarity-weighted, so matching a rare term is worth more than matching a common one. Use this whenever you have a question rather than an id, then follow up with get_entity.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Full-text search over the knowledge graph. Matching ignores accents and apostrophes, so query in the user's own words; every hit carries the fields it matched and a score. BM25 relevance: each query term is weighted by how RARE it is in this corpus and by where it hits (name 3, tags 2, questions 2, body 1). A hit must also cover a minimum share of the question's information, measured in the same rarity weights — matching only common words does not qualify. Centrality (how many objects point at this one) breaks TIES ONLY and is never part of the score, so it cannot make an irrelevant object rank. Two hits with the same matched_fields can still differ: the score is rarity-weighted, so matching a rare term is worth more than matching a common one. Use this whenever you have a question rather than an id, then follow up with get_entity.
    ConnectorNo auth
  • Full-text search over the knowledge graph. Matching ignores accents and apostrophes, so query in the user's own words; every hit carries the fields it matched and a score. BM25 relevance: each query term is weighted by how RARE it is in this corpus and by where it hits (name 3, tags 2, questions 2, body 1). A hit must also cover a minimum share of the question's information, measured in the same rarity weights — matching only common words does not qualify. Centrality (how many objects point at this one) breaks TIES ONLY and is never part of the score, so it cannot make an irrelevant object rank. Two hits with the same matched_fields can still differ: the score is rarity-weighted, so matching a rare term is worth more than matching a common one. Use this whenever you have a question rather than an id, then follow up with get_entity.
    ConnectorNo auth
  • Calculation, not advice. Verify with a professional before acting. Deterministic mortgage refinance break-even analysis. Given your current loan (balance, rate, remaining term) and a refinance offer (new rate, new term, closing costs, optional points), computes: - monthly P&I savings; - the cash-flow break-even month (Senaro's formula: total refinance cost divided by monthly savings, rounded up to a whole month, built on the payback test the CFPB toolkit describes); - the interest delta over your remaining-term horizon, and each loan's interest over its whole schedule (the current loan's remaining term, the new loan's full term); - a term-matched scenario that isolates the rate cut from a term reset; - a term-reset-trap flag (a longer term and a lower payment, but more interest over the new loan's full term than over the current loan's remaining term); and - the economic break-even (net-worth crossover) month under an equal-outflow model: both sides spend the same each month; the side that keeps the current loan starts with the upfront refinance cost invested at month 0 (nothing when costs are rolled in); money not spent on a payment is invested at investment_return_pct. The search runs to the end of the longer loan term, and stops earlier where a loan's term ends with money still owed. Rate-and-term refis only (cash-out and tax effects are out of scope). Pick this when refinancing your existing mortgage into a new rate and term is the question; pick `compare_mortgage_terms` when comparing two mortgage structures on a purchase you have not yet taken out. All defaults cite primary sources (LodeStar/ALTA closing-cost data, the CFPB toolkit's payback test). Scalar output, no chart series. payoff_months and payoff_month_shift use {status, value, explanation}; the two break-evens use {code, month, explanation}.
    ConnectorNo auth
  • The App Store search results for one term in one storefront, on one day: who ranked, in what order, with their names, subtitles and ratings. This is how you find out WHO took the places an app lost — a rank that fell is a fact, and the results page on the day it fell is the reason. Works for ANY term in the store, tracked or not, known to us or not: pass `keyword_id` for a term you already have an id for, or `keyword` + `country` for words a user typed, which resolves the term and crawls the storefront live when what we hold is over a day old. Omit the date for the most recent crawl. A lookup can persist a new shared keyword record and queue a background crawl that updates stored search observations. It does not track the keyword for your account.
    ConnectorNo auth
  • Add terms to one storefront's corpus, or take terms out of it. Add for a term the corpus SHOULD hold and does not — a rival's brand, a phrase Apple has never measured the popularity of, the term a thin storefront is really about; a pinned term is kept through every rebuild and refreshed on the same 72-hour cadence as the rest. Remove for a term that does not belong: ANY term can go, and one the heuristic found is also kept out of future rebuilds rather than returning within 72 hours. This is NOT `save_market`: seeds are what the corpus is expanded FROM and changing one re-runs the whole heuristic over that storefront, where these two writes act on single terms in the result.
    Connector
    Destructive
    No auth
  • Recommended first step for open-ended or topic discovery: free-text search across 14.5 million Smithsonian objects, with optional exact filters. Filters narrow by museum unit, object type, indexed date term, culture, geographic place, subject topic, named party, and online/CC0 availability. Returns curated summaries (title, date, museum, thumbnail URL, CC0 flag) with the total match count. The record_id in each result is the identifier for smithsonian_get_object, smithsonian_find_related, and smithsonian_get_media. To browse one exact category — a single museum, culture, date term, object type, or topic — use smithsonian_browse_category instead.
    ConnectorNo auth
  • Keyword/full-text search over the Canton Network knowledge base (CIPs, Canton/Daml/Splice docs, forum, mailing lists, whitepapers, grant proposals, blog, YouTube, GitHub). Canton-specific. Do NOT use for other blockchains, the web, or local files. Use this for exact-term/name lookups; use semantic_search instead for conceptual or 'how does X work' questions, and get_doc to read a full page once you have its id. NOTE: forum matches cover the topic TITLE and the FIRST POST only; a term that appears only inside a forum reply will not surface here, so use semantic_search (which indexes all forum post bodies) when a forum discussion is likely and this returns nothing.
    ConnectorNo auth
  • Buys a monitor: 30 recurring runs of citation_tracker_check for one prompt and 1 to 10 target domains, daily or weekly. The first run happens now and is returned. Later runs are read with citation_tracker_monitor_status using the returned monitor_id (the only credential; it is not recoverable). Each run flags which target domains changed since the last run. Paid once, $18 for the term ($0.6/check); no refund of unused runs; cancel any time with citation_tracker_monitor_cancel. Retains the prompt, domains and results until 30 days after the last run or until cancelled.
    ConnectorNo auth
  • Live one-off research for a search term: difficulty, traffic and effectiveness against whichever apps currently hold the top results. No history is saved -- use this to compare candidate terms before deciding what to track.
    ConnectorNo auth
  • List accounts the current user has access to, with optional name filtering. USE FOR: "which accounts do I have access to?", "show me my accounts", "what accounts can I manage?", "what is my account ID?", "which account am I logged into?", "what role do I have?", "show me account named X", "do you have an account called X?" AUTH METHODS: JWT tokens (OAuth) | PAT tokens (prefix "pat-") ARGS: - name (optional for regular users, REQUIRED for super users unless `account_id` is given): partial account name to search for. Super users span the whole platform and would otherwise return an unbounded list, so a search term is mandatory for them. If a super user calls this with neither `name` nor `account_id`, the tool returns an error asking for one — re-call with the user's intended search term. - account_id (optional): exact account id to look up. Use this instead of `name` when the search term is a number ("account 4368", "the 12057 account"), since account names are not ids and a numeric name search finds nothing. It satisfies the super-user search requirement on its own; supplying both narrows to accounts matching BOTH. RESPONSE FORMAT (identical for JWT and PAT — the token format does not change the result): Regular users: user_id, email, default_account_id, is_super_user, token_type, accounts[{account_id, name, role}] Super users with neither argument: error response — supply `name` or `account_id` and retry. Super users with name: matching accounts platform-wide (paged at 20). Super users with account_id: the single matching account, or an empty list when no account carries that id.
    ConnectorAPI key
  • Search NVD for CVE vulnerabilities by product or component name. Returns CVE ID, description, severity, and CVSS score. Search terms are matched against CVE description text and EVERY word must appear, so pass the product name ("OpenSSL", "log4j", "nginx") optionally with a technical term ("buffer overflow") — not a plain-English question. Use when researching security threats or checking if a known vulnerability affects your systems.
    ConnectorNo auth
  • Search available CDC PLACES measures by name or category. Returns matching measure IDs, names, and categories. Use this to find the correct measure_id for other tools. Categories: Health Outcomes, Health Behaviors, Prevention, Health Status. Args: keyword: Search term (e.g. 'diabetes', 'smoking', 'prevention', 'heart').
    ConnectorNo auth
  • Pure keyword (BM25) search — fastest option, optimal for exact-term lookups: paper titles, author names, method names (e.g. "LoRA", "RLHF"), arXiv IDs. Does NOT use semantic vectors. Use this when you know the specific term you're looking for. For paraphrased or conceptual queries, prefer "search_semantic" or "search". ★ Ranking is over at most 20 000 matching chunks: a COMMON term (or any_words over several) overflows that, and then pool.keyword.truncated=true says the ranking covered only the earliest-stored matches — narrow the query to get a full ranking. This is what keeps an answer under a few seconds instead of minutes.
    ConnectorAPI key
  • Add (or update) glossary entries for a project in one call. Pass an array of term rows, each with its own source and target term and their project_language ids — so a single source term can have a different translation per target language. Resolve the language ids first with get_project. Entries are upserted on (project, sourceTerm, source, target); re-adding an existing key updates its target term and its do-not-translate flag. Set doNotTranslate on a row for a term that must be kept verbatim (a brand or product name); its stored target term is then forced to equal the source term. Both terms are trimmed of leading and trailing whitespace before they are checked and stored; a source term empty once trimmed is refused. Marks any matching translation-memory entries stale so future translations pick up the change. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.
    Connector
    Destructive
    OAuth
  • Stop tracking a search term for an extension, across every store it was tracked in. Positions already recorded are kept; only the tracking stops. Other extensions tracking the same term through their own store listings are unaffected. A store listing can itself be shared by several extensions, though — when it is, they share one tracking, and removing the term from one removes it from all of them. A term is tracked per store language. Tracking "ad blocker" in en and again in de gives two independent keywords with their own positions. Call list_keywords for the languages an extension already tracks. Needs an ExtensionDash account. Without one, find_listing and get_store_listing still read any extension's current store page; sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page for anything else.
    ConnectorNo auth