Skip to main content
Glama
478,137 tools. Updated 2026-08-26 04:06

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

  • Find US medical codes whose official descriptions match a described concept, via full-text search over the bundled index. Every search term must appear — matched first as a token prefix, then as a substring so inflected and compound forms are also found (a "neuropathy" search surfaces "mononeuropathy"/"polyneuropathy" siblings too, not only a standalone "neuropathy" token). Filter by `system` (ICD10CM/ICD10PCS/HCPCS/RXNORM), `billableOnly` to exclude headers/categories, and `chapter`. Use when you have a clinical description and need the code — the reverse of medcode_get_code. Results echo the resolved system per row for chaining, rank exact prefix matches ahead of substring-only matches with a deterministic tie-break, and disclose truncation with a `nextCursor`: pass it back as `cursor` to page through the full ranked set.
    Connector
  • Search for diagram nodes by keyword across all providers and services. For targeted browsing when you know the provider, use list_providers -> list_services -> list_nodes instead. Args: query: Search term (case-insensitive substring match). Returns: List of matching nodes with keys: node, provider, service, import, alias_of (optional). Sorted by relevance: exact match first, then prefix, then substring.
    Connector
  • GET /search — Cross-resource omni-search Cross-resource search across profiles, rooms, messages (incl. private DMs + group DMs you're in), events, and chapters in one round trip. Returns the top-N matches per resource, grouped by resource. Use this when you don't yet know which resource carries the answer — agents typically call this first, then drill into a specific `GET /search/<resource>` for more depth on a single bucket. There's no page param: when you hit the per-resource limit and want more, switch to the per-resource endpoint for that one. The events slice has a baked-in forward-looking default (events ending in the last 30 days or later, and currently enabled) — this matches the in-app "Search across DC" surface. Use `GET /search/events` directly to look further back in time. **Query syntax (`q=`):** plain words match with prefix + typo tolerance. Wrap a phrase in double quotes to require an exact ordered match — e.g. `q="remote work"`. AND/OR/NOT/parentheses are NOT parsed in `q=` — use the structured filter params below for boolean composition.
    Connector
  • 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.
    Connector
  • Get full specifications, equipment, all images, and pricing per term for a specific vehicle. Use a vehicle_id from search_vehicles results. IMPORTANT: Always show `detail_url` as a clickable link — it points to the FINN configurator where the user picks term and km. To produce a direct checkout link for a specific term + km combination (and optionally a one-time Fahrzeugbereitstellung), call `get_subscription_pricing` and use the `checkout_url` it returns. Never construct checkout URLs yourself. The `vehicle_id` field is an internal API identifier — never display it to users.
    Connector
  • RETURNS QUOTABLE PASSAGES (page-level snippets + citation URLs), matched by KEYWORD/term. PICK THIS to find a quote or textual evidence on a topic across the whole library. → If the modern word won't literally appear in historical texts, use search_concept (matches by meaning); to list which BOOKS cover a topic use search_library; to dig inside one known book use search_within_book; if the user named an author/work, get_book first (its AI summary is usually the right first read). Query tips: single distinctive terms ("memory palace", "wax tablet") work best; multi-word natural-English queries ("unity of the intellect") may return fewer results because matching is term-based, not phrase-based. Each snippet has a snippet_type — "translation"/"ocr" means it is a verbatim extract from the source text; "summary" means it is AI-generated description (do not quote those as the author's words). Response includes total_matches, returned, and offset for pagination. Cross-cultural tip: for pre-modern or non-Western topics, search source-tradition vocabulary rather than modern English terms — e.g. for seminal economy search "jing" or "bindu" or "istimnāʾ", not "semen retention"; for female homoeroticism search "tribade" or "sahq", not "lesbian". The corpus is indexed via period translations that use tradition-internal terminology.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Resolve a human term to the canonical Open Food Facts tag ID that off_search_products filters on. Covers categories, labels/certifications, allergens, additives, countries, NOVA groups, and Nutri-Score grades. Pass a search term to resolve against the Open Food Facts vocabulary, which holds tens of thousands of tags; omitting it returns only a small reference list for each facet except NOVA groups and Nutri-Score grades, which are complete. Most tag IDs use the "en:" prefix (e.g. "en:organic", "en:gluten-free", "en:milk"); NOVA groups return bare digits "1"-"4" and Nutri-Score grades bare letters "a"-"e". Pass the id through to off_search_products exactly as returned. Category tags are frequently plural ("kombucha" resolves to "en:kombuchas"), so use the returned id rather than constructing one.
    Connector
  • 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 are by TOPIC TITLE only; a term that appears only inside a forum reply will not surface here, so use semantic_search (which indexes forum post bodies) when a forum discussion is likely and this returns nothing.
    Connector
  • [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)
    Connector
  • 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)
    Connector
  • Update a TAGGING RULE (dashboard: 'Tagging rules') — not a Keyword Monitor entry (those are Watchers; see watcher_update). Rename its term (pass `keyword`), set what it refers to (pass `description`), and/or pause/resume it (pass `active`). Renaming keeps already-tagged records on the old tag; new matches use the new term. 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)
    Connector
  • Search job listings on Jobily.gr, the Greek job board. Filter by free-text term, role/location/sector slugs, company, employment type, workplace type and work time. Use lookup_roles_and_companies, lookup_locations and list_sectors to discover valid slugs — unrecognized slug filters are reported in matchedCriteria.unrecognizedTerms and ignored by the search. Returns up to 20 jobs per page with the total count, facet counts (first page) and recovery suggestions when nothing matches. Search results do not include job descriptions — call get_job with a result's guid for the full posting. When total is large (100+) and few filters are active, recommend the user narrow their search using the facets or lookup tools rather than paginating through hundreds of results.
    Connector
  • Retrieve proteins annotated with a functional term or descriptive text in a single species. You can query for tissues, compartments, diseases, processes, pathways, and domains. IMPORTANT: For cross-species comparisons, run this tool separately for each species. Select relevant model organisms to search or ask user to provide the selection. The results reflect annotation depth within each category; use caution when interpreting. If no results are found, try simplifying the query. For tissue queries, follow BRENDA tissue nomenclature and omit the word "tissue" (e.g. use "skin" instead of "skin tissue"). Output fields: - category: Source database of the matched functional term (e.g. GO, KEGG, Reactome, Pfam, InterPro). - term: Exact identifier for the functional term. - description: The free text description of the term. - proteinCount: Number of proteins annotated with that term - preferredNames: Full protein-name list when `detail_for_term` is set - stringIds: STRING protein identifiers when returned - preferredNames_omitted: True when a row omits the protein-name list - stringIds_omitted: True when STRING identifiers are omitted
    Connector
  • Search academic references (journal articles, book chapters, theses, books, reports) by keyword and metadata. `keyword` is a single substring match over title + abstract, so search ONE term per call (combined terms like 'pèlerinage Mecque' miss results). References are multilingual: try French and English title/abstract keywords when relevant; metadata/filter values such as `reference_type` and `language` use French labels. Results include a short abstract snippet — use get_reference for the full abstract and bibliographic detail.
    Connector
  • Browse published Bible verse collections. Search by keyword, filter by language, sort by popularity. Each result includes the collection's raw cover `image` — the URL the publisher set, or null if they set none (the app may still show an auto-generated cover when null). This is the stored value, not the computed display image. Args: search: Search term to filter by name, description, or publisher name. language: Language code prefix (e.g. "en", "de", "ja", "zh"). ordering: Sort order: -downloads (default), -created, name. limit: Number of results (1-100, default 20). offset: Starting position for pagination.
    Connector
  • Browse published Bible verse collections. Search by keyword, filter by language, sort by popularity. Each result includes the collection's raw cover `image` — the URL the publisher set, or null if they set none (the app may still show an auto-generated cover when null). This is the stored value, not the computed display image. Args: search: Search term to filter by name, description, or publisher name. language: Language code prefix (e.g. "en", "de", "ja", "zh"). ordering: Sort order: -downloads (default), -created, name. limit: Number of results (1-100, default 20). offset: Starting position for pagination.
    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
  • Keywords observed in Amazon's own autocomplete suggestions for a seed term, per marketplace: the current suggestion list(s) for the seed's prefix (each term with its position 1-10 within that list) plus related observed vocabulary starting with the seed, with the marketplaces each term was observed in. Use for listing/backend keyword language, 'what do buyers type for X', or seeding niche/product research with real buyer phrases. No volume figures and no organic-ranking data — observed suggestion vocabulary only. Amazon marketplaces only.
    Connector
  • Search products by a term Arguments: term - the search term to look for products. It should be at least 3 characters long. cursor - optional, used for pagination. If provided, it will return the next page of results after. Pagination: Supports pagination with 'cursor' arguments. If 'cursor' is not provided, it will return the first page of results. Value for 'cursor' can be obtained from the 'nextCursor' field in the response. If 'nextCursor' is null, it means there are no more results to fetch. If value of cursor is null (or a string representation of 'null') dont send it in the payload. Results: Each product includes 'requiresFileUpload'. When true, the product has a required file-upload option (e.g. "upload your design") and shouldn't be added to cart through this assistant. Do not attempt to purchase it — tell the user it must be ordered on the website. Flow: - Call this tool with a 'term' argument and optionally with 'cursor' to search for products. - if you find a matching product, call 'get_product_details' with the product ID to get its variants and options (if any). - if 'requiresFileUpload' is true, inform the user the product needs a file upload and cannot be purchased here. - Call 'add_item_to_cart' with results of 'search_products' and 'get_product_details' (variant) tools to add the product to the cart. - [IMPORTANT] If product has variants ask user to pick
    Connector
  • 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.
    Connector