Skip to main content
Glama
817,855 tools. Updated 2026-11-21 19:12

"A search tool for finding academic research with Farsi-language search support" matching MCP tools:

  • "Find research software for [task]" / "academic / open-source tools for [field]", search research software registrations in OpenAIRE. Use for finding citable scientific software tied to published research.
    ConnectorNo auth
  • Search open-access research papers by keyword (e.g., "machine learning healthcare"). Returns titles, authors, abstracts, DOIs, and download links. Useful for literature reviews and finding academic sources.
    ConnectorNo auth
  • Search JobYap job postings by natural-language query. Matches job titles, falling back to significant keywords when the full phrase finds little. Returns result ids, titles and citable URLs for use with fetch. For structured filtering (location, company, remote, freshness) prefer search_jobs.
    ConnectorNo auth
  • Search Portugal listings by describing the property in plain language, matched against listing text by meaning rather than keywords. Use this for wants that are not filter fields — 'a renovated loft with exposed brick', 'quiet, lots of natural light, close to a school', 'a ruin to restore with a sea view'. Prefer search_properties when the request is entirely structural (typology, budget, location), and this tool when it is descriptive; combine both by passing structural filters here too, which are applied as hard constraints while the description only ranks. Results are ordered by relevance, so `total` is the number matching the structural filters, not the number that fit the description.
    ConnectorNo auth
  • Returns the plain-language meaning and step-by-step fix for one Malinois finding. Use it while helping the user fix an issue reported by scan_app, or when they ask what a finding means. Pass the rule_id exactly as scan_app returned it. Read-only, no network, instant.
    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

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Enables searching academic literature via Semantic Scholar with relevance filters, batch metadata retrieval, and citation-graph recommendations.
    5
    AGPL 3.0

Matching MCP Connectors

  • Academic research search across PubMed and arXiv

  • Web search for AI agents. Ranked results with page passages already extracted, plus URL to markdown.

  • Adds one check to a finished research and returns the id of the new child research. Use it when the scan skipped a stage, when a person asks about one phrase in particular, or to rebuild the report after new checks. A niche scan already runs the usual checks by itself, so this tool is for what is missing. Checks added this way are free: they do not spend researches of the plan. Checks of a demand research (`kind`): - `competitors`: who holds the search results for a phrase of the research; pass the phrase in `phrase`. - `dynamics`: two years of demand history. - `appstore`: App Store apps for the phrase with ratings and freshness. - `wiki`, `radar`, `youtube`: public interest and community signals. - `paid`: paid search for the phrase and its strongest candidates: volume, advertiser competition, cost per click. - `insight`: a summary of the findings written by the language model. - `report`: the final niche report, written anew from the current data; needs a finished niche scan. Checks of a child research: - `fingerprint`: product sites found by a competitors check, with pricing and app links; the parent is that competitors check. - `reviews`: recent App Store reviews of the leaders; the parent is an App Store research. - `insight` also accepts a competitors check as the parent. The parent must be completed and belong to the account. The check runs in the background: poll get_research with the returned `id` every 20-30 seconds until `status` is `completed`. `insight` and `report` are rebuilt at most once an hour.
    ConnectorNo auth
  • Search SaidItHere for real-world software dilemmas, framework gotchas, tool fatigue, and battle-tested community consensus workarounds from Reddit, Hacker News, GitHub, and Stack Overflow. Usage Guidelines: - Primary discovery tool: use FIRST when investigating bugs, library gotchas, unexpected price hikes, or developer complaints by keywords. - Sibling routing: follow up with 'get_problem(slug)' using the discovered dilemma slug to inspect full evidence quotes, sources, and step-by-step workarounds. - Sibling routing: if 0 matching dilemmas are returned, use 'suggest_dilemma' to queue the topic for crawler consensus synthesis. - Do NOT use for generic language syntax lookups or textbook documentation queries. Behavior & Side Effects: - Pure read-only, safe, and idempotent query without side effects. Does not modify user, session, or database state.
    ConnectorNo auth
  • Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.
    ConnectorNo auth
  • Open an interactive sutta viewer inside the chat — Pāli + English, plus an optional third row in the user's own language translated BY YOU. Renders each segment as: Pāli on top (canonical), the bilara-data English below it (verification anchor), and — when you supply `translations` — your translation in the user's language, clearly badged as AI-generated. Prefer this over dumping raw segments when the user wants to *read* a sutta. - `sutta_id` — standard SuttaCentral id, e.g. `sn56.11`, `mn10`, `dn22`. - `around` — a segment_id (e.g. `dn22:18.1`, from a search hit) to centre on; that segment is highlighted and scrolled into view. Use this after a search so the reader lands on the exact cited line. - `offset` — 0-based segment index for paging long suttas (use `next_offset` from the previous result). Do NOT combine with `around`. - `window` — segments before/after `around` to include (default 12). 🌐 **Translating for the user (important):** when the conversation language is neither English nor Pāli, you SHOULD translate the displayed segments and pass them via `translations` so the user reads in their own language while still seeing the originals: 1. Fetch the segments first (`get_sutta` with the same selector) so you have the exact Pāli + English text. (Already called this tool without translations? The result contains the segments — translate them and call this tool AGAIN with the same selector plus `translations` to upgrade the view.) Your translation must travel through the `translations` parameter to appear in the viewer — writing it as a normal chat message leaves the viewer bilingual and looks broken; the tool always accepts `translations`, so never report it as missing. 2. Translate **from the Pāli as the source, using the English as a semantic guide** — never relay-translate from English alone. Preserve untranslatable doctrinal terms (dukkha, jhāna, taṇhā…) as loanwords with a brief gloss instead of forcing equivalents. 3. Call this tool with `translations=[{segment_id, text}, ...]` covering ONLY the segments being displayed (never a whole long sutta), `translation_language` (BCP-47, e.g. "th", "es"), and `translation_disclaimer` — one short line IN THE USER'S LANGUAGE saying the translation is AI-generated in this conversation and should be checked against the Pāli/English above. Translations are conversation-ephemeral: nothing is stored server-side; the canon stays Pāli + English only. Translations whose segment_id is not in the displayed window are dropped (reported in `translations_dropped`). Without `around`, shows the sutta from the top (capped for long suttas).
    ConnectorNo auth
  • 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
  • Present a selection of tours or activities to the traveler as a visual list of cards (photo, rating, price, booking button) rendered inline in the conversation. Showing cards is the default way to present tours to the traveler: whenever your reply features specific tours (recommendations, a shortlist, availability results), call this tool alongside your text instead of waiting to be asked. Don't re-render a selection you already showed unless it changed. Call it AFTER finding tours with the search tools — it is a presentation tool, not a search tool. If you already checked availability with get_product_availability, you can pass each item's sessions (date and start time) and the cards will highlight them with booking links preselecting the date. For clients without UI support the same data is returned as structured text.
    ConnectorNo auth
  • Full-text search across all SEC EDGAR filings since 2001 for a keyword or phrase. Wraps EDGAR's own full-text search index, so it covers every filer and form type, not just a single company. Useful for finding who is disclosing a particular risk, technology, litigation, or event across the entire market. When to use: cross-company research ("who is disclosing AI-related risk factors"), finding filings that mention a specific term, litigation or regulatory tracking. When NOT to use: you already know the company (use edgar_filings_feed, which is company-scoped and cheaper), or you need results from before 2001 (EDGAR full-text search does not cover that far back). Args: - query (string, required): search text. Wrap an exact phrase in double quotes, e.g. "\"material weakness\"". - forms (string[], optional): restrict to form types, e.g. ["10-K"]. - dateFrom (string, optional): ISO start date (YYYY-MM-DD). - dateTo (string, optional): ISO end date (YYYY-MM-DD). - limit (integer, optional, default 10): maximum hits to return (1-50). Returns structuredContent: { "query": "material weakness", "totalMatches": 10000, "totalIsApproximate": true, "count": 2, "hits": [ { "id": "0001193125-26-123456:doc.htm", "entity": "Example Corp.", "form": "10-K", "filedAt": "2026-03-01", "cik": "0000320193" } ], "source": "https://www.sec.gov/edgar" } "totalMatches" is a lower bound and "totalIsApproximate" is true once EDGAR's own count exceeds its display cap (10,000) — narrow with forms/dateFrom/dateTo for a precise count.
    ConnectorNo auth
  • Ranked unified search for equivalent terms across multiple medical terminologies. Use this tool to: - Find the same concept in different coding systems - Compare how terminologies represent a concept - Support terminology mapping and data integration Searches across: ICD-11, LOINC, RxNorm, and MeSH. Set `target_terminologies` to limit which are searched, or set `source_terminology` to exclude one (e.g. when you already have a code from that terminology and want equivalents elsewhere). The two combine: source is subtracted from targets. `limit` caps candidates per terminology (default 5, max 10). Every candidate carries `match_score` (lexical similarity to the search term, 0-1) and `rank` (global position across all searched terminologies) — both computed by this server, since upstreams don't expose comparable relevance scores. Candidates from different terminologies whose titles are lexically identical are clustered in `groups` — a strong same-concept signal (absence of a group is NOT evidence of non-equivalence). Searches upstreams in English. For official pt-BR content, use the dedicated tools: `icd11_search`/`mesh_search` accept `language: "pt"`, and `cid10_search` is natively Portuguese.
    ConnectorNo auth
  • Use this when someone asks to see their blog posts, drafts or published articles, optionally for one blog, language or slug. Returns id, title, language, slug and published state, most recently edited first, 25 per page by default with a cursor. It filters by those fields and does not search the text. Not for reading a post.
    ConnectorOAuth
  • Use this when someone asks to see their blog posts, drafts or published articles, optionally for one blog, language or slug. Returns id, title, language, slug and published state, most recently edited first, 25 per page by default with a cursor. It filters by those fields and does not search the text. Not for reading a post.
    ConnectorOAuth
  • Starts tracking search `terms` for a project and returns `added`, the number of new keywords. Pass terms as an array of plain search phrases (terms: ["seo tool", "rank tracker"]) with the projectId from add_project or list_projects. Terms are lowercased, and one already tracked is skipped, so calling again is safe. Adding measures no rank: call check_rankings for positions. Search volume and difficulty arrive within about ten minutes, looked up in one request pooled with other keywords, costing one keyword_lookups unit per keyword; read them with list_keywords.
    ConnectorNo auth
  • Open-ended discovery across SMI deep reports, research bundles, and exports when you do not already have a record id — finds candidates by subject name, url, or keyword and returns typed references to pass to fetch. If you already have a record id from the conversation rather than from a search result, call the specific tool instead: smi_get_deep_report or smi_get_export to read one record, smi_check_order_complete for order readiness, smi_list_deep_reports or smi_list_exports for filtered listings, smi_get_report_findings for findings within a report. Deep reports and research bundles are filtered server-side by subject first/last name, broadening to an unfiltered fetch ranked client-side (across id, name, url, summary) when the filtered fetch finds nothing; exports match on url.
    ConnectorOAuth
  • Search the recipe collection semantically (dense + ColBERT hybrid) to gather the members of a theme. Pass a rich natural-language concept, not just a keyword — e.g. 'cozy cold-weather baked desserts', 'bright summer salads with fresh vegetables', 'Latin American and Caribbean mains', 'anything featuring apples'. Returns up to `limit` compact hits {id,title,cuisine,dietary,cookbook}. Call once per theme concept; call again with a broader/narrower query if a group is too small or too big. Do NOT rely on cuisine labels alone — many recipes are unlabelled and only reachable by concept search.
    ConnectorOAuth
  • Search the chain's hotels (worldwide, several thousand) by location, stars, brand, status and amenities, with pagination. All filters are optional and combined with AND. Always pass `country` (ISO code, e.g. "FR") together with `city` when the country is known or implied: a search on "Paris" alone returns Paris (Kentucky, US) and Paris (Ontario, CA) before Paris (France). Returns {"language", "total", "offset", "limit", "count", "next_offset", "hotels"}: `total` is the number of matching hotels, `next_offset` is null on the last page. Each hotel is a summary (hotel_id, name, brand, city, country, state, stars, status, lat, lng, cover_photo); use get_hotel_details for the full record. Geographic search: give a center (lat + lng, or near_hotel_id) and radius_km. Results are then sorted by distance, each hotel gets a `distance_km` field and the response a `center` field. Coordinates you supply for a landmark are approximate, so prefer a generous radius. Hotels without coordinates are excluded. No availability, rates or booking: this tool only returns descriptive information.
    ConnectorNo auth
  • Search the PUBLIC Awareness knowledge graph — 1,000+ sourced scientific papers. Use this when the user (especially a researcher or a research agent) asks for peer-reviewed findings: "latest evidence on X", "highly-cited papers about Y", "what does the literature say about Z". This is NOT a memory tool — it does not read the user's private memory, and it needs no per-user API key, so it works even when Awareness memory is not configured (the MCP connection itself still needs its own token). Coverage: condensed-matter, quantum-information, materials, machine-learning, renewable-energy, chemistry, biology, medicine, neuroscience, computer-science (2022-2026, cited >= 50), plus a business supply/demand domain. What comes back (anonymous preview mode): title, snippet (preview), confidence, source_ref (DOI), citation_count, domain/topic, and a detail page URL. Full content is NOT in the preview — tell the user it is paid retrieval via POST /api/v1/public/retrieve with an API key (see https://awareness.market/en/knowledge for the KaaS product). Args: query: Natural-language research question or keywords (2-1000 chars). domain: "science" (default) or "business". topic: Optional sub-topic slug, e.g. "medicine", "condensed-matter", "supply-chain". Empty = search all topics in the domain. top_k: Max results, 1-20 (default 5; anonymous callers are capped at 3). include_graph: When true, also return same-topic related items. Returns: {"results": [{id, title, snippet, confidence, source_ref, citation_count, domain, topic, url}], "related": [...], "total": int, "mode": str} `mode` is "preview" (anonymous) or "full" (authenticated).
    ConnectorNo auth